Salut,
bsimonssays wrote:
> I'm making a lot of progress with Grizzly. At this point my server has a
> custom protocol parser and echoes back the request that has been parsed.
Great!!
>
> What I'm curious about now is what the best practice is for the threading
> model of processing a request. Do you typically do the business logic in
> the same Worker Thread that has called the filter?
It really based on your application/protocol. For GlassFish v3, we are
using the WorkerThread for processing the http requests, but in Sailfin
we are using another set of thread to process the SIP protocol requests.
Or is it common to have
> a thread pool that the filter submits jobs to?
I would think it is really based on your application. Can you share what
you are working on?
A+
-- Jeanfrancois
>
> Thanks,
> Bill