good name to dispatch events (naming convention)

[puzzlecracker]

public delegate MessageHandler(Request request)

public sealed class Connection{


public event MessageHandler handler;


private void ExecuteMassageHandler(Request request)
{
if(handler!=null)
handler(request);
}
}


What's a good name, perhaps conventional, used in the place of
ExecuteMassageHandler?

Thanks

 

[Jeff Louie]

PuzzleCracker... Consider the convention:

public delegate void MessageEventHandler(object sender, MessageEventArgs
e);
public event MessageEventHandler Message;

protected virtual void OnMessage(MessageEventArgs e)
{
if (Message != null)
{
Message(this, e);
}
}
}

Regards,
Jeff
ExecuteMassageHandler?<<

 

[Dag Sunde]

public delegate MessageHandler(Request request)

public sealed class Connection{


public event MessageHandler handler;


private void ExecuteMassageHandler(Request request)
{
if(handler!=null)
handler(request);
}
}


What's a good name, perhaps conventional, used in the place of
ExecuteMassageHandler?

OnMessage()?

 

[Jeff Gaines]

What's a good name, perhaps conventional, used in the place of
ExecuteMassageHandler?

I used to use FireMessageHandler, but have recently changed to
RaiseMessageHandler as it seems to be more widespread.

 

[Pavel Minaev]

public delegate MessageHandler(Request request)

public sealed class Connection{

          public event MessageHandler handler;

        private void ExecuteMassageHandler(Request request)
        {
               if(handler!=null)
                   handler(request);
        }

}

What's a good name, perhaps conventional, used  in the place of
ExecuteMassageHandler?

If you were using the standard signature - "(object
sender, ...EventArgs e)" - for your event (and you really should!),
then you could use the rest of the pattern, in which case the method
is the same name as event with the prefix "On".