Got compressed serialization/deserialization done, and am working on RPCs now. What do you think, should RPCs be able to receive input parameters? Parameters for RPCs seem to make things much harder to implement efficiently and with a simple interface. Right now, gamestudio's RPCs (proc_client/proc_local) don't use parameters I think.. Not using parameters seems to offer very little improvement, though, since the event functions are pretty much Remote Procedures invoked by sending a certain MessageID.

Quote:

LOL why 4 connections!?


I might want to sell a full featured version, not sure yet.

Quote:

After quick test: server.c use 100% CPU.


You can set a higher ThreadSleepTime when initializing the network engine. This should decrease the CPU usage.

Quote:

I'll have to try again with client, but if I type a string for the chat it is supposed to show error malfunction?


Yes I use the error() instruction for quick & dirty output. This is in the Lite-C code, so you could obviously process the incoming chat message differently in a real application.

shader tutorial