A few months ago I ran into a similar problem and what I did was quite
simple. I registered the HttpServlet as a service with a property
indicating to which URI's it matched. A simple router servlet then
matched them up. Probably similar to Restlet but the use of OSGi
services makes it trivial to use.
Kind regards,
Peter Kriens
SEH> David Leangen <[EMAIL PROTECTED]> writes:
>> How is the performance?
SEH> I'm not sure, as I've only used the client half of it so far, so I
SEH> haven't tested the URI dispatching portion.
>> If I use the router, will it slow things down, or will the performance
>> degradation be negligible?
SEH> Not having looked at the implementation, I would expect that the router
SEH> is going do some regexp matching, collecting match groups into variables
SEH> for later retrieval, which is a little more than the conventional
SEH> servlet URI prefix matching. Given the rest of the work that will likely
SEH> be done in a dynamic Web application, the dispatching step is probably
SEH> negligible.
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
