Movie A is waiting for net connections
Movie B tries to connect to Movie A
Movie A decides not to accept the connection (bad password, banned
userID, etc) so it's WaitForNetConnection handler returns False instead
of True.

From what I can tell, no message is sent to Movie B, it justs seems to
sit idle waiting for an answer. Is this correct?

I would like Movie B to inform the user that the connection was rejected
and why. The only way I can think of doing it is for Movie A to actually
accept the connection request, send a message that the password was bad,
then have Movie A break the connection.

Is there a better way?

Dave C wrote:
> Movie A is waiting for net connections
> Movie B tries to connect to Movie A
> Movie A decides not to accept the connection (bad password, banned
> userID, etc) so it's WaitForNetConnection handler returns False instead
> of True.
>
> From what I can tell, no message is sent to Movie B, it justs seems to
> sit idle waiting for an answer. Is this correct?
Normally, movie's B muXtra should reply with a message containing an
errorcode.
Try to connect to movie A using this movie:
http://goMU.rebus.gr/Examples/Connec...MU-connect.dir
and see if you get an error message

>
> I would like Movie B to inform the user that the connection was rejected
> and why. The only way I can think of doing it is for Movie A to actually
> accept the connection request, send a message that the password was bad,
> then have Movie A break the connection.
>
> Is there a better way?
I'd recommend using custom authentication code: allow all users to
connect, no matter the id, and then ask them to provide their true
id/pass. You can then allow them to continue, or disconnect them.
That way, you can also have a descent registration page, within your movie.

Doh! I had used setNetMessageHandler to capture the "ConnectionProblem"
message, but I forgot to actually create the handler! In fact if
WaitForNetConnection returns FALSE the ConnectionProblem message is sent
to both movies.

Of course the error code is the generic -2147216214 error, so if I want
user to know explicitly why the connection request was rejected, your
suggestion sounds like the way to go.