[jdev] [ANN] Wildfire 3.0 Beta and Wildfire Enterprise

[Matt Tucker]

Stephen,

It's essentially doing connection aggregation. And, yes, the client
maintains the connection to the CM for the life of the session. To a
client, the CM looks exactly like any normal XMPP server.

The are some other interesting use cases for CM's. For example, an
external HTTP binding proxy could use the CM protocol on the backend to
be more scalable.

Regards,
Matt 

> -----Original Message-----
> From: jdev-bounces at jabber.org 
> [mailto:jdev-bounces at jabber.org] On Behalf Of Stephen Pendleton
> Sent: Thursday, June 22, 2006 10:25 AM
> To: 'Jabber software development list'
> Subject: RE: [jdev] [ANN] Wildfire 3.0 Beta and Wildfire Enterprise
> 
> Matt, out of interest - does the connection manager aggregate 
> many c2s connections into a smaller set of streams or does it 
> handle the authentication process and pass authenticated 
> streams to the Wildfire server or does it do something else? 
> Does the client maintain a connection to the connection 
> manager for the life of the session?
> 
> Thank You,
> Stephen
> 
> -----Original Message-----
> From: jdev-bounces at jabber.org 
> [mailto:jdev-bounces at jabber.org] On Behalf Of Matt Tucker
> Sent: Wednesday, June 21, 2006 8:33 PM
> To: Jabber software development list
> Subject: [jdev] [ANN] Wildfire 3.0 Beta and Wildfire Enterprise
> 
> 
> Hey all,
> 
> A few announcements today. First, Wildfire 3.0 beta is now 
> available. It includes two major new features:
> 
> * Connection manager architecture. Connection managers are 
> light-weight processes that handle load by aggregating client 
> connections to a core Wildfire server. Multiple connection 
> managers can be deployed to handle very large numbers of 
> users. We're developing the connection manager protocol as a 
> JEP, which we hope to make available soon. Our Open Source 
> implementation of the protocol is available at:
> 
> http://www.jivesoftware.org/wildfire/connection_manager.jsp
> 
> 
> 
>