Event Handler naming convention

Coordinator
Apr 29, 2008 at 4:28 PM
I would suggest to follow naming conventions especially when it comes to the term "sink".
How about only calling eventhandlers "sink" when they return void - which means a 100% filter or swallowing all readevents. Similar to the SQLSink event handler.
Whith this naming convetion on could easily determine wheter a specifica eventhandler can be used at any position in the event queue.
Developer
May 16, 2008 at 11:31 AM


mlandler wrote:
I would suggest to follow naming conventions especially when it comes to the term "sink".
How about only calling eventhandlers "sink" when they return void - which means a 100% filter or swallowing all readevents. Similar to the SQLSink event handler.
Whith this naming convetion on could easily determine wheter a specifica eventhandler can be used at any position in the event queue.



I tend to agree with this line of thinking completely.
Can we go ahead and rename the existing file and msmq event handlers to remove the "sink" from the name?