Should I use multi threaded applicationadapter?

[snacktime]

We are using red5 for a flash game.  I was thinking that ApplicationAdapter was event based/single threaded, but apparently it does use threads for things like handling remote method calls from the client to the server?  In any case, which is the correct adapter to use?  I wrote my code to be non blocking.  We are anticipating thousands of concurrent connections, or as many as we can push red5 to serve.

Chris

_______________________________________________
Red5 mailing list
Red5@...
http://osflash.org/mailman/listinfo/red5_osflash.org

[Walter Tak]

Some parts of this message have been removed. Learn more about Nabble's security policy.

That isn't a bad idea as long as your application is thread-safe ofcourse. E.g. if you update public properties make sure they use (atomic) locks etc.

 

Especially with thousands of users online it's a matter of seconds before two users will try to write to the same property.

 

Walter

----- Original Message -----

From: snacktime@...

To: red5@...

Sent: Thursday, 12 November 2009 03:23

Subject: [Red5] Should I use multi threaded applicationadapter?

We are using red5 for a flash game.  I was thinking that ApplicationAdapter was event based/single threaded, but apparently it does use threads for things like handling remote method calls from the client to the server?  In any case, which is the correct adapter to use?  I wrote my code to be non blocking.  We are anticipating thousands of concurrent connections, or as many as we can push red5 to serve.

Chris

---

_______________________________________________
Red5 mailing list
Red5@...
http://osflash.org/mailman/listinfo/red5_osflash.org

_______________________________________________
Red5 mailing list
Red5@...
http://osflash.org/mailman/listinfo/red5_osflash.org