Hi James,I talked to Wes a few weeks ago about the possibility of Influxis having a pricing option that was similar to LCCS pricing... based more on usage rather than max number of connections.Some consumer applications like mine, have very low predicatability and a high degree of variance around max simultaneous connections. Are you guys considering including a pricing option that would help us out? I would also be interested to hear if there are other products built on LCCS that have the same ...

Thanks Jeff. This is incredibly good news.

Thanks for the update Jeff,Your efforts to make this happen are VERY MUCH appreciated.- Barry

Me too.

@phaseblue - I understand your point. Each of are using different subsets of LCCS that are unavailable anywhere else and we have built businesses on the belief that this platform would be around long enough for those businesses to mature to the point where we could invest in building those components ourselves. Our best hope is that Adobe helps us by extending the shutdown date by at least an extra year. In your case, just like mine... the XMPP layer of LCCS is vital for these collaborative comp...

I can't say what Adobe uses for cluster management and failover of FMS servers, but I don't think this forum is the place to coordinate an effort to rebuild this or other components of the LCCS platform. I don't believe components of LCCS can be plugged in piecemeal. It's a complex platform with some components that could be open sourced easily but other components that are either proprietary to Adobe(screen sharing), tied into internal Adobe systems(payments) or licensed from 3rd parties. Any e...

In response to amma-adobe,FMS is just one component of LCCS, but FMS does not do it's own load balancing and fail over. Some of the components required for LCCS fail-over are technologies that require a license. This is another complication as far as open sourcing is concerned I would think.Barry

Thanks Jeff,The fact that you are looking at possible options is great news. This is wholeheartedly appreciated.One additional aspect I'd like to add to the conversation is that if Adobe has costs/losses associated with keeping the service up and running, the developement community should be polled about our willingness to pay more for the service. I'm sure there are people in the same position as myself who had planned for much greater use of the service once our products have gone into product...

I would also be interested in any kind of cooperative efforts to keep a version of the service alive.

If open sourcing isn't an option it doesn't seem like it would take a lot for Adobe to find a partner willing to provide hosting services for the product. It sounds like they don't care. We can rebuild all the parts of LCCS that we use without too much difficulty, but we invested a lot of time in getting the solution with LCCS tested of ready for production. Any complex application built on LCCS is going to require a lot of testing once it is rebuilt on other technology. When Adobe released LCCS...