Some people in a Sphere forum said they asked the RunUO guys about ConnectUO and the protocol for it but they never got a reply. They had the impression that they wanted RunUO to be bound tightly to ConnectUO. I hope this is the case because that would serve as excellent motivation to get this thing up.
From what I gather (and this comes from the RunUO forum), the protocol is simple, and ConnectUO can only handle what is called "RunUO + UOG" requests. I'll have to investigate this more later... It looks like this:
Code:
0xF1 0x00 0x04 0xFF
RunUO responds with:
Code:
RunUO Items=XXX, Mobiles=XXX, Clients=XXX, Mem=XXX
I'll replace RunUO with POL, throw in an item, mobile and online count and the memory could be configurable, unless the POL core started keeping track of physical memory, or computer stats in general (processor speed, hard drive size, available space, number of processors, operating system, etc...).
I think there's already a stastics script for the webserver (if there isn't, there used to be!). I could put all the computer specs into a config file so other scripts could use the info.
Still trying to dig around and learn more about UO Gateway protocol...