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:
My aim is to have 2 web application in the same OSGI container (1 OSGI
container consumes less memory than 2 OSGI container). The first application is
dedicated to public http requests, and the second application is dedicated to
admin http requests (on a different network card). By using 2 different network
port for each web application, I'm able to inject firewall rules to authorize
requests for the first web application from everywhere, and to restrict the
access to the second web application for admin request only.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
