A network component

Here is what I thought about a network component.

I imagined one component for connecting to a socket as a client, and one other component to let a application becoming a server.

Nigel Gerrard sent me a experimental socket component. But having no component programming documentation, the component had problems: how to poll sockets, for example?

Note: you have a Gambas API function named GB.Watch that tells the interpreter that he must watch a file descriptor.

The client component will almost be the same as the socket component Nigel did.

But the server component will be something more sophisticated. It will transform a Gambas application into a true TCP/IP server.

The programmer will just have to specifiy a port number and a protocol. The component will do all the polling, all the accept stuff, and will manage each connection in the same process (no fork, no thread, the interpreter won't support them).

The Gambas programmer will have nothing to do. As simple as possible !