Kind of, perhaps. But there's not really much that I have left to solve. Somebody on #perl commented that basically I'm doing a kind of HURD. The server itself is a small core with several independent support services around it.
The server already works, as well as the parsing. Basically, that's the largest problem I have right now. If I can fix it, pretty much all that is left is to design a proper protocol, and add handlers. | [reply] |
pretty much all that is left is to design a proper protocol, and add handlers.
Heh. You probably don't realize that you did the easy part, and the hard part is what's ahead.
Designing a protocol that is clean, transparent, scalable, and reusable is a royal pain. If you had leveraged off SOAP or Jabber, you'd also have the advantage of interoperability and pre-existing mindset and docs.
Good luck, because it looks like you're doing things the hard way.
| [reply] |
But that's not really the point of what I'm doing :-)
If I wanted to simply get my server done then I'd probably take Jabber and modify it for my needs. But that's not very fun.
I'm precisely writing it to have problems like the one I had and learn how to solve them. At the moment, I don't know how to properly write a server that uses XML for communication. I want to learn how. Just plugging a module that does it for me takes out the fun of it.
I also want to try some design ideas I have in mind. Some of them look like they wouldn't fit very well in the design of existing servers.
| [reply] |