gnelib-users

[GNE]GNE 45 Release Canidate 1

[Gillius <gi...@ma...>]

Elias (and others),

GNE 0.45 RC1 is now in the CVS.  The code is done but I haven't updated the 
readmes and stuff.  Like from 0.003 to 0.40 this is a HUGE release.  The 
user API has not changed a lot but the GNE code that implements it is 
DRASTICALLY improved and changed.  There were so many holes and bugs in the 
old version if is wasn't ideal conditions that it was like swiss cheese.

Please update your CVS version of GNE and run all of the programs and tests 
and let me know if there are problems with any of the programs.  exnetperf 
should be fine but I need to look over its code again and I am also not 
done implementing it (ie it works for only one client now), but still 
report issues with that other than it works for only one connection.

I am hoping this new revision of the code is SERIOUSLY rock-solid and I 
mean seriously so (at least for what is implemented).  Like if your 
computer explodes in the middle of connection while the connection is going 
but the client is processing onNewConn and sending and receiving at the 
same time, everything should terminately cleanly with no mem leaks or 
crashes.

Now the event system is GUARANTEED to be only one thread accessing events 
at any time and event order is now GUARANTEED and behavior guaranteed 
rather than saying it does but in the worst scenarios it breaks down.  IE 
before if an error occured between certain lines it might cause two events 
to happen at the same time, or events to become out-of-order, or objects to 
be destroyed while other threads are executing methods of that object.  
This happens no more!  Now the API is defined and is specfic for every 
single little place and between each action what happens if an error occurs 
or some other event occurs including which events came before and which 
events follow and which objects will be destroyed and when.  If you see any 
holes please let me know.

Gillius

[GNE]Re: [GNEdev]GNE 45 Release Canidate 1

[Elias P. <el...@us...>]

> Please update your CVS version of GNE and run all of the programs and tests 
> and let me know if there are problems with any of the programs.  exnetperf 
> should be fine but I need to look over its code again and I am also not 
> done implementing it (ie it works for only one client now), but still 
> report issues with that other than it works for only one connection.
>

Ok, as we already talked in IRC, i get some issues with exnetperf:

That one time, the following happened:

I hit a key in the server, and it closed and wrote:

Assertion failed: connections.find(socket) != connections.end(), file src/Connec
tionEventGenerator.cpp, line 104

The client wrote this:

Socket failure: Network error when trying to write to connection.

and stopped responding to key presses.