[Red5] appConnect invoking client call

[Walter Tak]

That's because the client isn't accepted yet.

If it would allow an invoke that would mean that pending new users would receive broadcasts from the room before you would have been authorized by appConnect().

Just let your client call a method on the server after it got a good connection.

Run an scheduler on the server that would kick all users that haven't called that certain method within say 10 seconds after they got in the room.

It's a workaround but not too hard to implement.

Walter

  ----- Original Message ----- 
  From: Jake Hilton 
  To: red5 at osflash.org 
  Sent: Wednesday, 15 October 2008 23:19
  Subject: [Red5] appConnect invoking client call


  Been searching through the archives.. and it seems there is not a work around for calling an invoke on a client connection within the appConnect method.. I've tried putting the call in the roomConnect and the appJoin methods but it doesn't seem to work.

  I know red5 has a rejectConnection method.. how much work is it to add an acceptConnection method as well?

  Thanks for a great project!

  Jake



------------------------------------------------------------------------------


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



------------------------------------------------------------------------------


  No virus found in this incoming message.
  Checked by AVG. 
  Version: 7.5.524 / Virus Database: 270.8.0/1726 - Release Date: 15-10-08 07:29
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5_osflash.org/attachments/20081016/c0f5a105/attachment-0001.html