On Mon, 2012-08-06 at 14:56 -0400, Bill Speirs wrote:
> What we'd truly like to do is resolve a request based upon host first,
> then based upon URI. Certainly rolling-out a handler for /*, then
> having that handler call the other handlers based upon host/URI would
> work, but it feels ugly.
>
>
What we'd truly like to do is resolve a request based upon host first,
then based upon URI. Certainly rolling-out a handler for /*, then
having that handler call the other handlers based upon host/URI would
work, but it feels ugly.
Do you want me to open a JIRA ticket with patch to make
HttpAsyncS
On Fri, 2012-08-03 at 16:31 -0400, William Speirs wrote:
> The HttpAsyncRequestHandlerResolver interface only allows for
> resolving an HttpAsyncRequestHandler via URI, and
> HttpAsyncService.getRequestHandler() is marked as private, so
> extending that class to change functionality it's possible.
The HttpAsyncRequestHandlerResolver interface only allows for
resolving an HttpAsyncRequestHandler via URI, and
HttpAsyncService.getRequestHandler() is marked as private, so
extending that class to change functionality it's possible. What would
be the easiest way to change HttpCore-NIO to resolve a
