Carl, Thanks for the input. Authentication is definitely the way to go, and I would always do that.
I was just wondering if Red5 was somehow aware that a connection was from the same flash instance. -Mike Carl Sziebert wrote: > Mike: > > Are you authenticating your clients in any way? If so, then you could > store the user's credentials in a list and check against that list for > each new connection attempt. If you are not authenticating them, then > I would highly recommend you do so. Without some sort of security > implementation, it becomes much easier for rogue users to hijack your > content. > > Carl > > On 9/6/07, Mike <[EMAIL PROTECTED]> wrote: > >> How can I prevent a client from connecting twice? >> >> For example, in a chat application, it doesn't make sense for the client >> to be able to connect twice. >> >> To be clear, I want to do this server-side in Red5. >> >> I know that I can cycle through all of the current connections to Red5. >> How can I tell it is the same client??? >> >> -Mike >> >> >> _______________________________________________ >> Red5 mailing list >> [email protected] >> http://osflash.org/mailman/listinfo/red5_osflash.org >> >> > > > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
