[crossfire] Server code structure

[Nicolas Weeger]

Hello.


The server code is currently divided in libraries, but without a clean 
separation IMO.

For instance why is "rod_adjust" in server and not in "common"? (forcing users 
of common to declare a stub)


Should we just decide to put all code together and forget the 4 or 5 
libraries, or on the opposite try to really separate things?


I was planning (someday :)) to tackle the events system, and move it to 
common, probably, that could help separate the logic - event "item_created" 
that the server could hook for rod adjustment. This would enable to remove the 
various stubs.

But if we decide it's ok to keep libraries separate, that's fine by me too :)



Best regards


Nicolas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.metalforge.org/pipermail/crossfire/attachments/20201210/a2ac96b0/attachment.sig>