good :) we all need a piece of advice once in a while... does wonders :)

no thats not going to work. i have made some progress. the reason im experiencing this behaviour is because mousemove is being called after the call of mouseleave.

are you sure you still want asynchronous operation if all that is going on is a single connection? seems to me you're paying the bills but not getting the goods. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Happy New Year to all. We hope 2010 soon brings us automatic PRE tags! Until then, please insert them manually.

yes i have. but default behaviour is toggle between states. what i dont want.

.NET makes this stuff pretty straight forward. Server side, use a TcpListener to accept incoming connections from the client. Once accepted, which gives you a TcpClient, the ususal practice is to create a new thread and pass it the TcpClient and let it do its server side stuff. If the connection is likely to be brief, use the ThreadPool. On the client, just use a TcpClient to connect to the server. Generally, the connection stays open until either end closes it, or it *may* get closed due to inactivity timeouts - not sure. You can attach a NetworkStream to the TcpClient at both ends, so you just end up with a duplex stream you can read and write to. Cassini is a little web server from the early days of .NET which allowed people to develop ASP.NET applications. Have a look at the source of that for some patterns. http://blogs.msdn.com/dmitryr/archive/2005/09/27/474534.aspx[^] Regards, Rob Philpott.

If it is a one way communication (i.e. from parent to child) you may consider adding an overloaded constructor. If you want 2 way communication, then delegates would be useful. By the way, what kind of a communication you are talking about ? What objects would be passed to and fro ? Details would be great. Thanks ! "A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder coolestCoder

As others said, you can use binary serialization to send data over the wire. But take a look at projects like Protocol Buffers[^] also. There is a .NET port available and it makes data transmission easy and it does serialization and deserialization for you. Best wishes, Navaneeth

thank you!

ok i think i have figured out how resX works. thanks.