Wow, I take a weekend off the forums, and somehow manipulix takes over - I love it! Thanks for the assist! (am I the only one who thought of Asterix et Obelix during this thread?) nigel

The server to server APIs are in full swing and should be released with the next version of the SDK.Recording is going to take a little longer because we need to sort out, among other things, how to store and retrieve the recording files from external content repositories since we want to keep storing as little of your data on our servers as possible.

No, this was really something related to how the authentication servers in our architecture replicate the information. I don't work on that particulat part of the system so I don't have all the details on this. For the more collaboration-specific servers we have a distributed shared memory that mantains all shared information, authenticated users included, but in this particular case the problem was between the login request, that goes straight to the authentication servers and the first request...

Cool, take your time we are not monetising it anytime soon yet Thanks,Greg

The "too many attempts" alert is actually a runtime exception, is it not? You should be able to listen to the event : ConnectSession.ERROR. If you have a listener for this event, no runtime exception will be thrown. The general rule is : :: If there's no event handler for ConnectSession.ERROR, and an error occurs, we throw an exception so that you notice there's something wrong. :: If there is an event handler, we let you handle it (in your handler) and don't throw the exception. hope that clear...

Hi,Just verified now , it is working fine. May be some outage , please try and let us know.ThanksHironmay Basu

well, yes, actually we are currently forcing room names to belower case only (or case insensitive, if you want, since we alwaysconvert the room URL to lowercase before accessing it.)There isn't a real technical reason for this, apart that weare forcing account names to be lower case / case insensitive (forsome technical reason beyond my control :)) and for the sake ofsimplicity we do the same for room names.I guess this is not documented anywhere (sorry ):) yet.

Complete code is attached now. Because of weird restrictionerror in forum, it was taking time to attach the code in myprevious message.ThanksHironmay Basu

thanks for following up. Let me try and clarify.Say I have this code inside my session tag: The main app is set to 100% w and h, and so is the canvas andwhiteboard. Now have a look at thisfile and thisone, note how the pointer is incorrect (I am not using anycustom code). Also note that the shapes appear to be drawn in thecorrect position, but the cursor of the person drawing the shapeseems to actually draw it at a different point (the cursor appearsa few pixels offset from where the shape a...

Hi nigel,Maybe when we get the auth key for a user we could also makea call with the session manager on this user to attach some datarelated to this user.Once the user login he could receive the loginReceived eventcarrying the extra data for this uer in a dic ?The need to pass data when preparing room was just to addsome details to the users using the platform. their firstname,lastname, mail etc since these fields are known at the time of theroom creation, passing them could be handy.Greg

hello, to answer the question thank you for see this topic:http://forums.adobe.com/thread/452883many thanks for your help.lionceau,

Hi Barry,Yes you are right. You need to just set the publisherIDs to your own userID. It will then not subscribe to streams of any other user. And since, its only your stream, it will be taken locally. Hope this helpsThanksHironmay Basu

The warnings about the crossdomain.xml files are just warning(and one day I'll learn how I am supposed to change my pretty muchempty crossdomain file to please the new FlashPlayer 🙂I suspect (well, I am actually quite sure 🙂 that you don'thave a room called "foobar_53jBu9l40", even if I don't understandhow it got all the way to the "ticket stuff" before figuring outthe room didn't exist.

thanks Hironmay got it .

I finally took the time to look at the example, and I have noidea of why I named everything "room" instead of "account"(actually, I know. My original example was dealing with a singleroom).Anyway, thanks for pointing it out. I update the example andit'll be in the next version of the SDK.

Well, my Python skills only go so far 🙂Thanks for finding this. I'll get it fixed for the next SDKrelease.

Cool, we're always interested to see how people work withCocomo in other Flex frameworks. Do report back to us how thethread you posted turns out - I can only watch so many threads atone time 🙂 nigel