Alex Russell wrote:
> This is so freaking cool. How's the message rate across
the back
> channel? Is it using JMS internally?
No currently it is using all terracotta. They distribute
state
well - so the clients, channels and subscriptions are well
distributed.
For the actual message events, I am using their distributed
method
facility.... which is known to be slow and also is
broadcast, so it
will suck all clients into all nodes. So not usable for
real.
I am working with the terracotta folks to come up with a
better
mechanism for that.
I may also try a JMS cluster, but that will be harder to
cluster
state such as subscriptions.
cheers
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cometd-dev" group.
To post to this group, send email to cometd-dev googlegroups.com
To unsubscribe from this group, send email to
cometd-dev-unsubscribe googlegroups.com
For more options, visit this group at http://grou
ps.google.com/group/cometd-dev
Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---
|