|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
|
|
q: rejectClient(msg);how do i interprete/ catch/ consume this in flash?
thx tom _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);If you mean with this message (warning: request for
a bit more information next time you post something, please) ; how can I detect
in Flash if a client is being rejected by Red5 (disconnected) rather than a
failed netconnection then the answer so far is ; not.
Unless it has been changed (maybe someone can
verify) you cannot pass variables/parameters with the rejectClient method like
an error code.
The easiest thing to do is:
1. invoke a method on the client with an
error-code/message
2. let the client disconnect itself after that
message
3. queue the id of the client on the
server
4. let the server disconnect all clients in the
queue in a scheduler
Used this approach and it works like a
charm.
Make sure you check if a client still is connected
else you might see some exceptions while trying to disconnect a client that
isn't there anymore.
_______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);My observations show that the application property will have the error message.
event flash.events.NetStatusEvent (@1cf9e389) [inherited] info Array (@1ce48939) application "you were rejected" code "NetConnection.Connect.Rejected" description "" length 0 level "error" objectEncoding 3 On Thu, Jul 9, 2009 at 3:18 PM, tom <tomabroad@...> wrote: how do i interprete/ catch/ consume this in flash? _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);thx to the both of u.
@walter: i like ur approach @dom: what do u use to "observe"? thx tom _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);I now see there is another rejectClient() method
with additional object parameters.
Nice to know for new projects. Tnx.
We prolly never got that to work (while fiddling
with ~ 0.6.1) and had to invent the workaround (which took a lot of extra work)
and ofcourse never bothered to check the docs again.
Btw is that url the current 'final' API
documentation site ?
_______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);Walter,
Like Dominick is saying, the NetStatusEvent's info object will hold the information passed to rejectClient(), as well as the code "NetConnection.Connect.Rejected". - TK
On Thu, Jul 9, 2009 at 4:19 PM, Walter Tak <walter@...> wrote:
-- And do this, knowing the time, that now it is high time to awake out of sleep; for now our salvation is nearer than when we first believed. _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);The only thing I'm a little confused about is why we put it in the application property instead of the description property where I think it would make more sense.
On Thu, Jul 9, 2009 at 7:36 PM, Tyler Kocheran <rfkrocktk@...> wrote: Walter, _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);Just set a breakpoint on your client inside the NetStatus handler. Then when you reject a client with rejectClient("Bad call"); you will see it in the debug variables view.
On Thu, Jul 9, 2009 at 7:00 PM, tom <tomabroad@...> wrote: thx to the both of u. _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
|
|
Re: q: rejectClient(msg);cool - thx
On Fri, Jul 10, 2009 at 10:33 AM, Dominick Accattato <dominick@...> wrote: Just set a breakpoint on your client inside the NetStatus handler. Then when you reject a client with rejectClient("Bad call"); you will see it in the debug variables view. _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org |
| Free embeddable forum powered by Nabble | Forum Help |