#5 Win32Network object needs a base class

[Chris Thomas]

I'm unhappy about the layout of the Win32Network
object, it's all top heavy and there is nobase classes
for things which are NOT win32 specific

of course, when it was designed, x-platform was NOT
considered very high on the list of things to do. but
now I would like to do a linux conversion I think it
would benefit me to start moving as much of the code
into a base class as I can, I'm sure it's more than
possible.

at the moment, I'm using win32 threads, I think I
should port this to pthreads, cause that is one step
towards x-platform code

the code uses winsock2 events to notify when data is
recv, so I'm going to have to think of a way to replace
that with a system which can work on other platforms
too, or make it so the system can be isolated into just
the win32 port and then make an alternate
implementation on another platform.

I'm sure huge parts of the Socket and ServerSocket code
can be migrated to x-platform base class. Just looks
like it's waiting to be done!!!

[Chris Thomas]

Logged In: YES
user_id=682144

There is now a full set of interface classes and cross
platform classes to base each platform layer upon, the new
class layout is as follows

1.Interface layer
2.cross platform layer
3.platform layer

the more code that can be put into layer 2, the better,
since then it would mean less platform code needed to
support more than one platform. although this idea has to
be tested some more, perhaps putting too much code into the
middle layer, limits what can be done with the platform
layer, perhaps new designs will fail to work with the cross
platform layer, without extensive modifications?