I already did something similar to what you want. Although I'm using regular sockets instead of UDP, the idea is roughly the same. I could send you what code I have later when I get home if you want?
Or I could just add you to the SVN so you can take the code from there.
Hm, yes, could be intresting to see how you solved some problems, still I need a UDP basis for a game, everything else is for a shooterlike game a real problem:)
Why not use JGN? It's customizable and powerful enough so that you don't have to reinvent the wheel.
-> Well it is far to complex for my needs, to much unused stuff, not transparent workflow
-> no support for loginsystems by house (or i never found them see first point)
-> as far as i see it no support for reliable transfer of UDP packets
-> it's serialize stuff does nto support complex objects well
-> Well it is far to complex for my needs, to much unused stuff, not transparent workflow
I dont think its complex, it just has lots of packages, most of them for the test classes.
It has exactly everything a game networking library needs. Client/Server, messaging, player abstraction and synchronization.
no support for loginsystems by house (or i never found them see first point)
A generic game network library shouldn't have that. You can add it quite easily yourself though, through the messaging system.
as far as i see it no support for reliable transfer of UDP packets
It does have reliable UDP transfer, your message class should extend CertifiedMessage interface which causes the client to send it several times until the server acks it.
it's serialize stuff does nto support complex objects well
What do you mean? Do you have an example of a complex object that failed to serialize?
I think you should give JGN another try. It's a stable and reliable networking library. I have used it myself for a small 2D MMO project and it saved me a lot of work.
Well the code is now ready for a first release , see first post