[Opentnl-general] Server vs Client objects

[boB G. <boB@Gage.net>]

I'm having some issues with ghosted objects.    In all the examples a world 
object, say a Player class that has TNL::NetObject at the base of its 
inheritance tree, has the same object on both server & client sides, 
meaning that the client has local methods that do server operations and 
vice-versa.

This results in a lot of methods of the form { if (isServer) { ... } else { 
... } }  Since we have separate teams developing server and client code it 
also means that both teams are inside the same files a lot, leading to a 
lot more CVS conflicts than "normal."  ( whatever that is :)    It would be 
preferable for us to have TNL play with abstract classes, with each 
application defining a final descendant, including all 
server|client-specific code at that level.

By default, TNL appears to require the same object on both sides of the 
connection, but is there a way to allow each application to have their own 
class that TNL plays with as the parent class??  ( much like the 
masterserver example uses an 'interface' class that each side descends it's 
own connection class from ).

Or did I have something completely different going on when I decided we 
couldn't define both ServerGame and ClientGame descended from a common Game 
object that TNL does all its magic on?  :-)


Thanks in advance!
boB