Hi, I learned about ongoing work for updating the HttpService spec yesterday at OSGi DevCon in a talk from Felix. Thanks a lot for those insights into the ongoing spec work.
There are a few things that I'd like to throw into the discussion that may (or may not) be of interest when updating the HttpService spec. One think that might be interesting is to have the ability to control which bundle (signer?) is allowed to register in which namespace. For example, if there is an set of administrative component registering things under /admin/... when I'd like to prevent other bundles in the system to also register under that namespace. Another thing is a clarification in the spec regarding the relation of HttpContext and HttpSession. The Equinox HttpService currently uses the HttpSession from the container for all registrations and all HttpContext. Thus everybody shares the same session data. However, some HttpService implementations create different sessions per context in the underlying container. That only works if one can do a real deep integration with the underlying container. However, the Equinox ServletBridge just has one underlying session. Maybe a HttpContext can define a prefix to session attribute keys (or something along the lines) that scopes the session data to a particular HttpContext? -Gunnar -- Gunnar Wagenknecht [email protected] http://wagenknecht.org/ _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
