Uses of Package
org.deepsymmetry.beatlink.dbserver

Packages that use org.deepsymmetry.beatlink.dbserver

Package	Description
org.deepsymmetry.beatlink.data	Offers rich information about the tracks loaded in players on the network.
org.deepsymmetry.beatlink.dbserver	Provides an interface to the database servers running on Pioneer players.

Classes in org.deepsymmetry.beatlink.dbserver used by org.deepsymmetry.beatlink.data

Class	Description
Message	Encapsulates a full dbserver message, made up of a list of Field objects, and having a particular structure, as described in the Packet Analysis document.
NumberField	A number field represents an integer, and can take up 1, 2, or 4 bytes, depending on the tag which introduces it.

Classes in org.deepsymmetry.beatlink.dbserver used by org.deepsymmetry.beatlink.dbserver

Class	Description
Client	Manages a connection to the dbserver port on a particular player, allowing queries to be sent, and their responses to be interpreted.
ConnectionManager	Manges connections to dbserver ports on the players, offering sessions that can be used to perform transactions, and allowing the connections to close when there are no active sessions.
ConnectionManager.ClientTask	An interface for all the kinds of activities that need a connection to the dbserver, so we can keep track of how many sessions are in effect, clean up after them, and know when the client is idle and can be closed.
Field	All dbserver messages are made up of lists of fields, which are type-tagged values.
Message	Encapsulates a full dbserver message, made up of a list of Field objects, and having a particular structure, as described in the Packet Analysis document.
Message.KnownType	Defines all the message types we know about, with any information we know about their arguments.
Message.MenuIdentifier	For many types of query messages, the first argument of the message is a 4-byte integer which we currently refer to as r:m:s:t, because the first byte is the player number of the player making the request, the second byte identifies the menu or destination for which information is being loaded, the third byte identifies the media slot (USB or SD) being asked about (as described in CdjStatus.TrackSourceSlot), and the fourth byte identifies the type of track being worked with (for most requests this is 1, meaning rekordbox).
Message.MenuItemType	Defines all the known types of entries that can be returned for a menu request.
NumberField	A number field represents an integer, and can take up 1, 2, or 4 bytes, depending on the tag which introduces it.