HI Jeff,

Thanks for your continued help with this. I fully understand many of these issues are totally out of your hands.

We do have an FMS Server, used in a different part of our company, and it’s as yet not something Ive been able to look at. There are others that are in charge of it.

What Im looking for is some understanding of how I would go about transferring our LCCS functionality onto the FMS server.

Bearing in mind that as of this moment I am starting from a point of zero FMS knowledge, apart from knowing it’s there and available for me to use.

The current FMS server in our company is used to with pre-built modules and we don’t have an FMS developer in house. It looks like Im about to become that person

Where do I even start lol

Initially, I would need to translate what we’ve been able to do with LCCS via our FMS Server.

Im really looking for any help, I can with this.

Bear in mind that today is effectively day one of my R&D time regarding this, and I thought contacting you could be a good start.

We have several projects that were due to be based around LCCS services that I now need to look at again with a view to running them via FMS.

My basic question,  where do I even start J

Anything would be helpful, even a list of resources or possibly to make contact with others here who are about to start the same journey.

Thanks as always Jeff

Regards

Glenn

Tinylion uk

As far as I can tell, LCCS was built on FMS and an XMPP server. ( google XEP-60 for more detail on the XMPP angle )

My current plan is to use FMS or Red5 with Openfire or eJabberd. It'll also need some glue to tie authentication and screenshare into it.

I think with a bit of effort, I'll be able to reuse most of the LCCS client code and have a pretty stable, maintainable system.

Does any one else have any plans yet?

Jeff,

A few months ago at the Flex Summit, Adobe announced that it would donate LCCS to the Spoon project.

http://www.spoon.as/2011/flex-summit-live-updates-day-2/

"Adobe will do the following…

Open source contribution of related technologies:

blazeds.net, server-side AS, LCDS, LCCS, TLF, Gravity, FXG, OSMF"

Is Adobe still going according to this plan, or this yet another broken promise from Adobe?

Because quite franklly, replacing hundreds of thousands of dollars of code is not a feasible solution. And considering Adobe's recent track record at taking care of its customer base, neither is reverse-engineering something that works perfectly well to work with another Abode product (FMS) with a now very questionable lifespan. Either find a way to migrate it to Spoon, or sell it as a standalone product like FMS so that the millions of dollars the industry has spent developing for this technology will not go to waste. Anything less is simply abysmally irresponsible.

Please Adobe, I am begging you, do not shut this down without migrating it to spoon or offering it as a standalone product like FMS.

Jeff, what should I do about screen sharing? You need to provide us with an alternative. I have thousands of sites using my code which uses screensharing. Now what should I do? This is a disaster.

Thanks for the clarification Jeff. Oh well, for a while there was hope.

Personally I have absolutely no interest in alternatives. The is no reason nor excuse good enough to can a perfectly good technology which many companies have invested millions developing for. Adobe, please find a way for someone to take up the torch. You owe us, your loyal customers and clients, that much.

Thanks.

Jeff, atleast allow us to create accounts for 3 more months. We have clients who use their own accounts for using our component. Now without account creation option, they are stuck and our component is rendered USELESS.

Adobe is ruining our business completely. We are really small and now we can no longer sell our component. I'm at loss of words. How can you have a migration plan so sudden. Google and all other companies offer a plan of atleast 6 months.

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 production. There may be other cost structures, including a simple rate increase, that would enable Adobe to keep it running for an extension of the currently planned shutdown schedule without that cost burden.

I'm not sure how relevant this suggestion is, but my point is that if bottom line cost is an issue, we should explore solutions.

Barry

thank you jeff for some encouraging news.  it's good to know that some discussion is still possible here. 

Thanks for the reassuring news Jeff!  When you say "ease the transition from LCCS", you mean transition from the brand and not the functionality, right?

And I would have no problem paying more for the service bandwidth as well!

Matt

I have been developing for a while on a new project with LCCS.  Having heard on the potential demise of it, I have a few pointers for potential alternatives.

If you just need shared data (not video, not screen sharing),  I really like union server: http://www.unionplatform.com/

If you want free, open source (I haven't found much on the flex side, but a lot on the server side) : http://www.bigbluebutton.org/    <- This has some awesome possibilities for a good LCCS migration.  I think if we all pitch in, we could probably convert it straight across with the Flex LCCS libraries we have.  Red5 does not do RTMFP, however.

Last but not least is Wowza & FMS.  An excellent comparison chart can be found here: http://askmeflash.com/article/10/comparison-wowza-vs-fms-vs-red5

The only reason my company decided to invest in LCCS was the ability to do remote viewing and controling.  Does anyone know of an alternative that allows for this?

Hi Barry,

Thanks for your response.

Are you saying that Adobe has licensed that technology from someone else?

I am wondering what that technology stack is, that is used to do LCCS

failover?

We could also possibly buy the license then, given that Adobe is not going

to support it any longer.

Is LCDS/BlazeDS part of LCCS or not?

Regards

This sounds great @mattcom.  I would be very interested.  I've been looking at Wowza - if we can simply replace the RTC components to interact with Wowza, that would save most of the time for developers. We could simply change the room URLs to point to another service and at least for whiteboarding, video, audio and chat, that could work.  Screen sharing is another beast.

When you say you are creating your own screen sharing, I am wondering if this would involve some kind of 3rd party plug in, are you simply capturing the Flash Player's display and sending it across the wire (I have found this to be quite slow) or have you managed to leverage the "builtin" adobe plugin that LCCS activates?  I ask because for what I am doing, the first solution is not an option as most of my users do not have rights to install new software (while the current LCCS solution worked fine).  Thanks in advance!

P.S.  Does anyone know if Adobe is monitoring this thread?  I have not seen them respond to much here and there are a lot of paying customers who are just looking for some kind of guidance.

Message was edited by: philswe

Not too sure about the Java Applet but these would be some very locked down corporate type PCs. 

You can capture an image of the stage but not the desktop so that is pretty limited.  I messed around with it awhile back and the problem was one of compression.  To do effective screen streaming you need a codec that simply sends compressed differences in the images and key frames (as the webcam does) and I never got past sending 4 frames a second.  Also, there was no remote control.  In all, unusable.

I was hoping that someone from Adobe would say, "Since we are cutting all you customers off, here is a way to leverage our built in technology".  Since they are leaving us out in the cold, I don't see what harm that could do.

Hi Jeff,

The OpenTok platform may be able to help your customers as they transition out of LCCS. 

TokBox, the company behind OpenTok, has been delivering live face-to-face video through the web since 2007.  We have helped American Idol, Coke and over 30,000 startups and websites bring the emotion of live video communication to their site or app. 

Our cloud-based OpenTok API makes it easy for developers to add face-to-face video to their applications without having to worry about infrastructure and scale.  We offer JavaScript and ActionScript libraries as well as a new iOS SDK.  With OpenTok, developers can control size, interaction and layout to support a range of use-cases: 1-to-1 video conversations, broadcasts and multi-party video calls.

http://www.tokbox.com/opentok/api/features

http://www.tokbox.com/learnmore