Few suggestions for netcode implementation of player.
Semi stable interface for the Player class.

The other possible solution is composition of two objects.

The virtual methods are the communications interface (View in MVC terms), the
rest is the model. Master sessions holds & communicates with the non-virtual
parts of the class, and uses the virtual parts to notify peers/the actual
players of changes.

Updated player-remote to reflect these changes.
Include guards.
Initial sketch of Dealer class.

This will be an instance of the master session that actually governs the game.
Will alse manage the dealer-as-player instance.
Simple example, non-mature implementation of the non-virtual Player parts.
Introduction of the socket-specific namespace sck

This is only in use in the Netplayer context and thus never exported.
Implements a thin wrapper around POSIX sockets
Semi stable interface for the Player class.

The other possible solution is composition of two objects.

The virtual methods are the communications interface (View in MVC terms), the
rest is the model. Master sessions holds & communicates with the non-virtual
parts of the class, and uses the virtual parts to notify peers/the actual
players of changes.

Updated Netplayer header to reflect these changes.
Merge branch 'lyc_b' into lyc
Experimental implementation of most of Netplayer class

Currently does no error checking or handling, but should provide a nice
starting point for implementing socket communcation abstraction.