BARRYC16

Re: LCCS Alternatives - Adobe LiveCycle

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 ...

2.1K

Re: LCCS Alternatives - Adobe LiveCycle

Thanks Jeff. This is incredibly good news.

2.3K

Re: LCCS Alternatives - Adobe LiveCycle

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

2.2K

Re: Petition to extend LCCS Service until October 31st 2013 - Adobe LiveCycle

Me too.

402

Re: LCCS Alternatives - Adobe LiveCycle

@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...

1.7K

Re: LCCS Alternatives - Adobe LiveCycle

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...

1.3K

Re: LCCS Alternatives - Adobe LiveCycle

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

2.3K

Re: LCCS Alternatives - Adobe LiveCycle

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...

2.3K

Re: Moving forward in light of the LCCS shutdown... - Adobe LiveCycle

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

268

Re: LCCS shuts down permanently December 31st. What's your plan? - Adobe LiveCycle

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...

579

Re: LCCS shuts down permanently December 31st. What's your plan? - Adobe LiveCycle

Yesterday's announcement wasn't exactly a surprise given the messaging that has been coming from Adobe recently, but what IS very surprising is that there was no contingency plan for business's that have been built on LCCS as part of the announcement.Surely Adobe has plans to either:a) Open Source LCCS, so that business's that have been created and invested in based on the availability of LCCS can host their own instances of the productorb) Give us some idea as to what the plans are for the code...

576

Re: Error With New SDK With Setting WebcamSubscriber.webcamPublisher - Adobe LiveCycle

Confirming that this is now fixed with Safari in the newly released 10.3 library. Was still seeing the problem only with Safari in the beta 10.3 swc release, but the issue is now completely fixed.

190

Re: AEC 10.3 swc - Adobe LiveCycle

I copied the playerglobal.swc into the SDK directory exactly as Arun describes above. I don't remember seeing any compiler errors when I moved to the 10.3 swc.

724

Re: AEC 10.3 swc - Adobe LiveCycle

Hi Matt,Can you post the errors you are seeing?I am using the 10.3 swc and have got it working by following the steps posted by Basu at the beginning of this thread. Is it possible that you are compiling with the older playerglobal.swc?Barry

747

Re: Error With New SDK With Setting WebcamSubscriber.webcamPublisher - Adobe LiveCycle

I still see this error but only on Safari browser.The workaround works fine for me but I have a question. If I call .subscribe() on my local subscriber am I still getting the cam feed locally if I set the .publisherIDs array to only have my own Id? Previously I wasn't calling subscribe() and I just want to make sure that I am not going out to the server to get my own feed if I call this method.Thanks,Barry

191

Re: problems logging in with authentication token. - Adobe LiveCycle

Thanks Raff,Yeah, in order to make my logic bullet proof I think I need to create the token at the time the user is about to enter the room. That way I can be guaranteed that they will be joined with the current existing session.I can see how I may have use cases whereby some users trying to enter the room might be tied to sessions that have been terminated, although I'm not completely sure this is what happened. It's certainly possible.In order to be 100% sure I'm going to go with your suggesti...

248

Re: problems logging in with authentication token. - Adobe LiveCycle

With the way I am creating tokens, there is potential that tokens could be created across different room sessions. Not sure if that explains the issue I saw yesterday but depending on how sessions are garbage collected on the server I think it's possible. Anyway, I am going to change my server side code so that I do a keep alive on all rooms until they are finished. A room that only has a single session suits my use case better, so using the keep alive API should help me to emulate that.I'll pos...

205

Re: problems logging in with authentication token. - Adobe LiveCycle

Has anyone else seen an intermittent problem with authentication tokens?It seems like once in a while an authentication token that I create using the server API doesn't work for me and I get a bad authentication key error. I can't seem to narrow down the pattern of when or why it happens. Is it possible that some authenitcation keys for a room get removed while others stay valid?I have a log file segment that shows the request info for a room I created this morning.6/26/2011 13:24:23.608 [INFO] ...

205

Re: AEC 10.3 swc - Adobe LiveCycle

I have no echo now with the new swc. Audio is getting close to perfect. I still make those two calls in the API, but not sure if it's necessary or not.Thanks.

745

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Thanks Nigel, Arun,Looks like the problem is fixed for us also. Just ran the same test and CPU is fine.Very much appreciated here also,Barry

178

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Hi Nigel,Just to add to this. My tests were also done with the 10.3 swc. Didn't test with 10.0.Thanks,Barry

174

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Hi Nigel, Arun,I just ran a test on my app and we still see significant problems. I see the Flash player on one of my machines going up to 70% CPU usage. It also seems like the memory footprint keeps climbing. On all machines the Flash player seems to just slow down a lot.This new version has definitely made a difference, but I think there are still issues here.I can go back to the 10.0 swc to see if that fixes things or is that a pointless experiment?Thanks,Barry

171

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Thanks Arun,I'll run a full test tomorrow.Thanks,Barry

172

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Hi Nigel,I'll wait until there's a 10.3 swc seeing as it seems like the problem is fixed.Thanks,Barry

173

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Hi Nigel,We just tried it with the 5 cams we've had problems with in our app, plus an additional 6th cam and we got no racheting either. There was also an extra naked dude cam in there... you might have a new Chatroulette on your hands if you don't take that down soon 🙂When you are rebuilding the swc, will it be the version that doesn't do peer assisted networking? That's the swc we are currently using in our app. If you want us to test with a patch swc, we can do this test any time.Thanks for ...

224

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Hi Nigel,Awesome. I'll run my reproducible case tomorrow afternoon.I owe you a Boddingtons 🙂Barry

224

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Hi Nigel,Just to clarify for my case the questions you asked in the previous post.Each client has a subscriber to each of the other clients, but only one is active at any given time. When a subscriber becomes inactive, the .close() method is called before the client starts subscribing to the other publisher.Also... I have one additional subscriber that switches between the publishers by changing publisher Ids. I never call the .close() method on that one because it's always subscribing to someon...

230

Re: Still a significant CPU ratcheting effect when changing PublisherIDs - Adobe LiveCycle

Hi Nigel,I think I may be seeing this exact same problem with the 10.3 library posted last week. I ran a test last night with about 10 users publishing in a room and it seemed like all of the flash players were crashing.I just ran a test today and saw the same problem with 4 cameras publishing to the same room.Seems like it's fine if I"m just publishing two or three cams, but I saw the CPU usage on one of my clients go up to 95% today on a 4 cam test.In case it helps... each publishing user can ...

226

Re: One-One Chat Application using LCCS - Adobe LiveCycle

Yep. It's basically the same idea but actually a bit easier. The code should be something like this...Cam: private function startPublisher() : void {// Removing the recipient ids on the publishing side. Everything should be handled ok by setting publisher ids on the receiving side for each receiver// var recipientIDs:Array = new Array();// var userId : String = Util.getUserIdForDisplayName(CocomoSession.session, this.currentTargetUser);// recipientIDs.push(userId);// webcamPub.recipientIDs = rec...

190

Re: One-One Chat Application using LCCS - Adobe LiveCycle

Here's some sample code that will help you to direct messages to individual clients:public var chatModel:SimpleChatModel;chatModel.allowPrivateChat = true;var message:String = "Hello"; var cmd:ChatMessageDescriptor = new ChatMessageDescriptor(); cmd.displayName = session.userManager.getUserDescriptor(session.userManager.myUserID).displayName; cmd.msg = message; var userId : String = getUserIdForDisplayName(session, targetUser); cmd.recipient = userId; chatModel.sendMessage(cmd); // This will get...

190

Likes given to

User

Count

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe