THello,
Continuation is initialized per default for all new comethandlers.
What about the Streaming usage case, where continuation is not needed ?.
Please correct me if im wrong, but to me it seems that the current comet
implementation is designed for the polling mode.
While looking in the CometContext.java it seems like alot of work to
rewrite to allow for pure streaming.
the handler hashmap is based around the id continuation init etc.
I see 2 ways of fixing this:
1.Make the current cometcontext.java alot more complex.
2.Introduce a baseclass or interface and let there be two different
implementations/subclasses,
for polling and streaming. CometEngine needs to be told what
implementation class to use.
The second option seems more future proof to me also allowing for something
users cant do today: making their own cometcontext implementation with their
specific needs.
Im anyhow willing to implement whats needed, with Arcands guarding eye.
what does mr Arcand and others have to say about this ?.
regards
gustav trede