Both look useful, although I'm not sure I understand how #1 actually works. It's late, so my brain's not working right, but could you explain it a little? :)
Also, a couple suggestions. Can you add a log message when you catch all Exceptions thrown when creating the PathMapper? That makes it easier to tell what went wrong when the error occurs :). And, the authentication header returned from #2 should probably be configurable since most app servers support more than just Basic authentication. That could lead to issues later. Nice work, though. I think I may end up using #2 sometime here soon. -James On Wed, 2005-02-09 at 20:21 +0100, Oliver Zeigermann wrote: > (1) A hook mechanism that allows a custom mapping from http request to > path and also can be used to pass the request to the store level > (2) Possibility to force (re-)authentication from the store layer - > especially from WCK > > This should not cause any backward incompatibilities and hopefully is > no problem for anyone. > > Comments? > > Oliver > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
