That should be "https://na2.collaboration.adobelivecycle.com" (the direct URL for the service). "collaboration.adobelivecycle.com" is the only host having the problem.

We are on it, and the problem should be fixed shortly. Sorry for the inconvenience

If you go to "portal.collaboration.adobelivecycle.com", after logging in, you can click on the big "SDK Download" button on the right.You'll be presented two options: choose the second one (Download just the SDK Contents Zip). Click on it and you should be able to download a file "payload.zip". Unpa...

Can you give us a concrete example of this use case ?You mentioned UserManager before, but in UserManager only UserList will get updated if, for example, a user enters or exits the room.

serverIntegration/ruby/lccs.rb. I just checked the latest download and it's there (you may have updated your SDK and something failed unpacking the payload.zip file - I have just noticed that in my "payload" folder the file was missing. We'll have to try to reproduce this case)Thanks!

Subscribing to a single node is currently not implemented in the back. Some of the language exposes it in the front end, but the value is ignored.I suggest you extend your "receiver" class to ignore values for nodes you don't care.

For playback in the current release you don't specify any user. The PlaybackAuthenticator does everything for you.You should use the same URL you used for recording (same room) and specify the same archiveID (of course if you did multiple recording in the same room, you'll use the archiveID related ...

Did you try connecting to DevPortal ? Does it fail there too ?If you are still having problems send me a pm with your account info and I'll see if I can find anything strange.

No, it's really that on some system curl works and streams don't and on some curl doesn't work.I picked the "stream way" as default because that's what worked on my machine There is really no difference in the way the two methods work, they both do https requests similarly and curl is one of the bes...

No, using curl is as secure as the other way. It's just that on some systems / versions one way works and the other doesn't