TServer and TClient extend what?
BlitzMax Forums/BlitzMax Programming/TServer and TClient extend what?| 
 | ||
| What should I call the root type for both the TServer and TClient types? TNetworkNode? TNode? TTerminal? THost? What seems like a proper name? | 
| 
 | ||
| TNetwork | 
| 
 | ||
| I like TNetworkObject. :) I'm not all that into the word "node". | 
| 
 | ||
| I like Terminal, but I'm not sure that is accurate. | 
| 
 | ||
| No a terminal is more like a client... since you connect a terminal to a host. The reason I suggested TNetwork, is that a Host/server and a Client are part of a network solution... just seemed logical. | 
| 
 | ||
| A network is made of multiple objects.  A single object in a network is not a network. | 
| 
 | ||
| TSocket (socket) is the correct system term. | 
| 
 | ||
| TNetworkArchetype? Because it's the definination of all the network objects. | 
| 
 | ||
| It's obvious: TComputer ;) | 
| 
 | ||
| The socket type is already taken by BRL. | 
| 
 | ||
| TGateway either have to pass through. | 
| 
 | ||
|  A network is made of multiple objects. A single object in a network is not a network.   Thats right... you need a client and a server | 
| 
 | ||
| I'm also building a multiplayer network library... I went with TNetwork since all it does is open UDP sockets on the currently functioning physical network.  so the "network" is made up of whoever I can send to or receive from. destination addresses are associated with the messages not the TNetwork class... messages are then sent on a particular network.  It's not great but I've not yet found anything I like better. | 
| 
 | ||
| TNetNode? TSubNet? TNode? TConnection? | 
| 
 | ||
| In my 3D Mud client I implemented them with these names: Type TMudClient Extends TMudNode ... EndType Type TMudServer Extends TMudNode ... EndType The only shared code in TMudNode was pretty much a dispatch method: Type TMudNode Method HandleMessage(node:TRemoteNode, msg:TGNetObject) ... EndMethod EndType | 
| 
 | ||
| I'm for TConnection given they don't form any kind of node realistically (they just handle messaging etc), I see no reason to name them as if they were | 
| 
 | ||
| TEitherAClientOrAServer | 
| 
 | ||
| TNetworkEntity Abstract | 
| 
 | ||
| TStopWorryingStartProgramming ;) | 
| 
 | ||
| TLeadwerkNet :) |