Re: [Once development] Network stuff ...

[Remi B. <rem...@la...>]

Cir...@cs... wrote:

>OK, So I had a look at the Wiki and I now understand what the network stuff is all about.  Hehehe... it's kind of funny in a way because in my previous message I happened to pick on the server code and the networking in particular, without really having a clue that the network stuff had been dropped in CS.  I think that's all the more reason to abstract things and do some serious reformulation of the code. Of course I'm not saying "throw everything out" -- 99% of code will still be of great value but will require some minor rework.  In the end we shouldn't be shackled by the details of CS or whatever other external libs we would like to use.
>  
>
The problem is that this require _way_ too much work. Look for example 
at ocoverlay.cpp. Think at a api that would make this file independant 
of aws. Or do you think ocoverlay.cpp is an example of an interface? In 
both case, this file need to completely rewritten if we change our 
windowing system. ocawsmgr.cpp would also need big adjustement, mainly 
due to aws signals system.

For data types, I think using csString and stuff is fine. After what i 
have seen and heard in the last months, these aren't subject to big 
changes often.

>So what do we do with network stuff?  Do we have enough programmers here to write a networking library?
>
No.

>  I'd volunteer for that sort of stuff.  Once again, I'd suggest a NET<>ONCE interaction via an API -- that way if someone doesn't like my stinking code they can use whatever they want as a replacement provided they implement the API and the API on the Network side is all accessed via an object like gNetIface (an implementation of the API). 
>  
>
You are welcome :)

>By the way, does anyone know what this "winmail.dat" crap that appears at the end of my messages is?  It's some stinking M$ webmail server tacking that rubbish on -- I'm using Linux/Mozilla.  Typical M$-- waste resources.
>  
>
Yeah, m$ is crap

Remi Bonnet