Hi Paul,
from what I see in the tests, the code bellow initializes Grizzly
Cometd adapter, which sits on the TCP port PORT at context-path "/
cometd/cometd" and ready to process client cometd requests.
Can you pls. elaborate a little bit more what you would like to have?
Thanks.
WBR,
Alexey.
SelectorThread st = new SelectorThread();
st.setPort(PORT);
st.setAdapter(new CometdAdapter());
st.initThreadPool();
((ExtendedThreadPool)
st.getThreadPool()).setMaximumPoolSize(5);
st.setEnableAsyncExecution(true);
st.setBufferResponse(false);
st.setFileCacheIsEnabled(false);
st.setLargeFileCacheEnabled(false);
AsyncHandler asyncHandler = new DefaultAsyncHandler();
asyncHandler.addAsyncFilter(new CometAsyncFilter());
st.setAsyncHandler(asyncHandler);
st.setAdapter(new CometdAdapter());
st.setDisplayConfiguration(true);
try {
st.listen();
} catch (Exception ex) {
ex.printStackTrace();
}
On Jan 26, 2010, at 13:54 , Paul.M wrote:
>
> Thanks for the response about Servlets. Knowing about the alias was
> one
> thing I was stuck on...
>
> How about cometd? Any even know of any blogs that explain how it's
> tied
> together? The example I saw seemed to call into the servlet which
> then
> connected to cometd somehow. Still confused on that.
> --
> View this message in context: http://old.nabble.com/Am-I-crazy--Yes...-tp27316206p27322199.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>