id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
130	spocket -- assorted good fixes	Fred T. Hamster	bugdock	"spocket:

   1. option for nonblock spocket:
         1. wouldn't it be nice if spocket could construct as non-blocking right off the bat?
   2. move some funcs into here from stack:
         1. the socket class should get functions from tcpip stack, like the select and such.
         2. offer two versions?: one for this socket and static for any socket.
   3. can spocket do swap:
         1. what if the spocket just swapped in the byte array from its own buffers?
         2. instead of requiring the parent to allocate a bunch of space?
   4. add open to spocket:
         1. need to implement that open method; do it by providing enums for the ways to open it.
   5. make sure receive is proper:
         1. this is a general concern for any users of spockets....
         2. the absolute proper way to do a receive is to have a very big buffer.
         3. otherwise it won't expect to get anymore than that. and you must always specify the actual size to be received.
   6. spocket is goofed:
         1. spocket is nuts.  why should it be using the ctor address if we're always binding to the any address?
         2. and the spocket send_to function is whacked.
         3. if the address passed to constructor is really the other side for a client, then we don't need the parameter in send to at all?


"	new-feature	assigned	minor		feistymeow-octopus