- From: Dean Pehrsson-Chapman <dean@...>
- To: users@...
- Subject: Fwd: StandaloneProcessor
- Date: Tue, 6 Aug 2013 14:42:34 +0100
I tend to get a lot of
I see a previous user who hit this issue was advised to use the filter
method. My particular use case is to use the shiny new connection pool -
how can a client grab a connection and do some work with a filter? I don't
understand the thinking behind the architecture here.
Any help gratefully received.
---------- Forwarded message ----------
From: Dean Pehrsson-Chapman <dean@...>
Date: 6 August 2013 10:16
After some fiddling about I've realised that synchronously using
doesn't work with a filter chain - the message is handled by the filter
chain and not reported to connection.read. Setting the processor to be a
StandaloneProcessor works fine, but that seems odd to me as now you can't
take advantage of the filterchain mechanism. Is it correct to say that
there are incompatible ways of doing sync client (or even async - a
completion handler will never be called either) and async server?
Or am I just doing it wrong?