On Sep 28, 2011, at 2:04 PM, Bram de Kruijff wrote: > got this question from a colleague who noticed the configuration > property "org.osgi.service.http.hostname" is in our web configuration > but it does not seem to do anything. Question is whether it is really > a dummy or not :s > > 0) The OSGi Compendium spec 4.2 does not specify this option (see the sepc) > 1) The Felix HTTP Service does not specify this property (see [1]) > 2) The Knopflerfish HttpService DOES specify this property (see[2]) > > KF says "Host (IP interface name) to open the HTTP server socket on. > An empty string means all available interfaces" which may actually > make sense. Anyone ran into this before and/or tried to bind to a > specific interface?
Looking at this from another angle: it's non-standard, we're not sure if anybody is using it right now, so let's just remove it. Btw, I can see the value of just binding to a specific interface, but if someone needs this, and is fine with using an implementation specific extension, then let him/her add this property in *their* configuration. We should not do so in *our* configuration. Greetings, Marcel _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
