Results 1 to 8 of 8

Thread: easySockets TcpClient Wrapper Class

Threaded View

  1. #1

    Thread Starter
    Junior Member
    Join Date
    Jul 2010
    Location
    Ohio, USA
    Posts
    18

    easySockets TcpClient Wrapper Class

    I wrote this class to inherit TcpClient and add some pre-written code for sending and receiving, synchronously and asynchronously, as well as connecting. Haven't gotten any disconnect code added in, but pretty much there's no real extrapolation to that function, so it's as simple as calling the base close command. I wrote this because I'm used to objects having properties, like Port and Address, that should be stored data for connecting, so that the info can be referenced later. Also because I looked at Asynchronous coding and thought to myself "well I could wrap up the code each time to do different things, or just have it throw an event for the ease of use." I preferred the event.

    I tried to make sure it was well-documented and clean.

    Please, I'd like some feedback on this: Is there anything that glaringly JUST WON'T WORK? Is there anything that SHOULD be in this? Is there anything that SHOULD NOT be in this? Any questions, comments, please, I'd love to know how it feels and looks.

    Thanks to jmcilhinney, formlesstree4, and Atheist for their awesome assistance in helping me make this code.
    Attached Files Attached Files
    Last edited by Gedrean; Jul 19th, 2010 at 04:39 PM. Reason: Added thanks line

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width