| Summary: | ECF Generic TCP server should not use 'localhost' as name | ||
|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Alex Blewitt <alex.blewitt> |
| Component: | ecf.server | Assignee: | ecf.core-inbox <ecf.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | slewis |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Alex Blewitt
Hmm. I think this is already working in my experiments with 3.5.1. Perhaps it's just the use of 'localhost' on the command line arguments in the example demos which is confusing me. This might be invalid, e.g. see TCPServerSOContainer.java which looks like it's overriding the default host appropriately. Maybe this bug should be changed to 'Support dynamic port numbers and update examples to use non-localhost and non-default ports' and priority lowered? (In reply to Alex Blewitt from comment #2) > Maybe this bug should be changed to 'Support dynamic port numbers and update > examples to use non-localhost and non-default ports' and priority lowered? This functionality is now available with the generic provider...via generic-provider-specific service properties. See under Remote Service Configuration Properties under: http://wiki.eclipse.org/EIG:Configuration_Properties#ECF_generic_provider |