Hello List !

I have actually started working on this side project, an experiment really - a chat client/server. There are of course some really great examples, from which I am borrowing a fair bit of code ;) (A few more comments throughout the sample projects wouldn't hurt :>). What I want to try and understand a bit better is how/why the use of a delimiter is necessary - it looks as though the EZprotocol uses chr(252) as a marker. Shouldn't there be some way when creating my own TCPSocket class, that there is some property or method I can create that knows (via the TCP protocol/socket in and of itself?) where the beginning and/or end of a particular data stream is ?

Also how much data can the socket buffer for me ? In other words, if I peek in on it periodically, and wait until I find *two* occurrences of my marker - how much data is that ? I'm expecting the chunks of data to be fairly small most of the time - easily fitting in a single TCP packet .. but say something like theoretically having to transfer a *large* userlist back to the client .. I'm in two minds about how to work this out. I'm thinking it may be a bad idea to attempt to break it down to discrete blocks of data, (although this seems like a simpler way to tackle it) - and instead be sure that the client/server can 'stream' large data sets correctly. The data is presented serially after all.

I consider myself to still be relatively new to RB although I own 5.5.5 and 2005R4 Professional licenses - Windows. I should mention that I'm a big fan of RB, and of these lists, and all the clearly very talented people who frequent them :) I switched from VB6 as soon as I discovered it! I have found it to be an incredibly useful tool, although I largely use it for my own custom work related
needs - this project is just for fun :)

James
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to