Genny Test v0.30 released, Mon, 7 May 2001 23:24:49

Greetings,
Changed and fixed:
Basic ignore command and rules implemented. I wrote get_from which returns a string of hexadecimal digits useful for the new ignore command. I added a list object to the control dict, 'ignores', which is a list of the hex strings mentioned above. I added the ignore command
(which I haven't documented but I'll fix that) which adds specified strings to the ignore list.
I changed a connection object. It is a class instance now and more complicated. It will have the address in itself and socket object and send function in itself. This is in preparation to simplify the identifiers/connections objects using references.
I decided that a 512 byte packet limit might not have any practical value. I have removed the limit and this version will accept packets of any size (except ones that don't have enough header). The check was broken anyways (I fixed the commented out version...).
I fixed a too-small packet check to account for the fact that the numeric byte is no longer compulsory.
I removed the double-check to see if a packet is marked with a supported service, so now genny is 0.0000000001% faster.
I changed control so I can specify None as a routing header if I like.
The chat service now takes advantage of the ignore infrastructure, it displays the hex string from get_from before each message. (You can then use the ignore command to ignore all further genny packets from that message.)
I changed the genny file service to be able to send HITS of maximum UDP size, and some HITS packets of large size have worked successfully.
I made raw_send more stubborn at sending and ignoring connection refused packets.
Oh and the release now includes the neglected protocol-control.html and protocol-info.html.
Plans:
I am going to make the broadcast identifiers be a pointer to a client identifier (or something like that). In addition, a client identifier will be a pointer to a connection instance. The connection instance will have a pointer to the socket object. So eventually I can stop specifying the main UDP socket object to each function. It would also make it easier to have connections have their own TCP connections.
And I'll toss a bunch of error messages and error message processing into the file service.
TomG

Home: Genny: Posts