Hello,
I'm had a curious look at Grizzly examples in latest branch ( 2.0). I could
see that you are using a number of filter chains there : transport, string,
multiline, clientauth and client. While I understand what each filter does,
I am kinda confused about the sequence of their call. I think that while
accepting a request (reading) all the filters are called starting from
transport to the client. Whereas, while writing, they will be called in the
opposite order..right? In the auth example, I see that clientauth filter
ends up calling the other filter. probably there is an explicit call to
other filters from clientauth filter. How is the sequence of the filter
supposed to work? Any pointer to reference material is much appreciated.
--
View this message in context: http://old.nabble.com/client-auth-filter-example-tp27752503p27752503.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.