You're right. However some port forwarding firewall rules can be a work around to the ip binding problem.
For the moment, I think that I will simply use 2 Osgi container: one for the frontend web application, and another one for the backend web application. Le 2 févr. 2010 06:55, "Rob Walker" <[email protected]> a écrit : If I understand you correctly, as well as the problem of different ports, and Richard's point on how to tell which HttpService to register aliases with (which could be worked around by convention that the HttpService publishes it's port as a service property - something I think we mod'd the original Felix jetty based service to do. But I think you have a bigger problem: (on a different network card) To achieve that you will also need each HttpService bind it's listener socket to just the local IP address for that 1 network card - which means your config will also need to specify a local IP address to bind the listener too as well as the port. Most HttpService implementations probably assume the listen will go to all network interfaces. - Rob Loïc Cotonea wrote: > > Richard has summarized my potential responses :) > > Here the reason why: ... --------------------------------------------------------------------- To unsubscribe, e-mail: users-...
