| Interface | Description |
|---|---|
| GameReadyObserver |
Used to inform interested parties when the
ParlorDirector
receives a game ready notification. |
| InvitationHandler |
A client entity that wishes to handle invitations received by other
clients should implement this interface and register itself with the
parlor director.
|
| InvitationResponseObserver |
A client entity that wishes to generate invitations for games must
implement this interface.
|
| ParlorReceiver |
Defines, for the parlor services, a set of notifications delivered
asynchronously by the server to the client.
|
| ParlorService |
Provides an interface to the various parlor invocation services.
|
| ParlorService.InviteListener |
Used to communicate responses to
ParlorService.invite(com.threerings.util.Name, com.threerings.parlor.game.data.GameConfig, com.threerings.parlor.client.ParlorService.InviteListener) requests. |
| SeatednessObserver |
Entites that wish to hear about when we sit down at a table or stand up
from a table can implement this interface and register themselves with
the
TableDirector. |
| TableObserver |
The
TableDirector converts distributed object events into
higher level callbacks to implementers of this interface, which are
expected to render these events sensically in a user interface. |
| TableService |
Provides table lobbying services.
|
| Class | Description |
|---|---|
| DefaultSwingTableConfigurator |
Provides a default implementation of a TableConfigurator for
a Swing interface.
|
| Invitation |
The invitation class is used to track information related to
outstanding invitations generated by or targeted to this client.
|
| ParlorDecoder |
Dispatches calls to a
ParlorReceiver instance. |
| ParlorDirector |
The parlor director manages the client side of the game configuration and matchmaking
processes.
|
| TableConfigurator |
This should be implemented some user-interface element that allows
the user to configure whichever TableConfig options are relevant.
|
| TableDirector |
As tables are created and managed within the scope of a place (a lobby), we want to fold the
table management functionality into the standard hierarchy of place controllers that deal with
place-related functionality on the client.
|
Copyright © 2015. All rights reserved.