Package org.transitime.ipc.data

This package contains the low-level objects that are transmitted to the clients via RMI.

See: Description

Class Summary

Class	Description
IpcActiveBlock	For IPC for obtaining currently active blocks.
IpcAvl	A serializable object used by RMI to transfer AVL data to client.
IpcBlock	Configuration information for a Block for IPC.
IpcCalendar	A calendar object for IPC via RMI
IpcDirection
IpcDirectionsForRoute	Contains each direction for route, along with each stop for each direction.
IpcPrediction	Contains information on a single prediction.
IpcPredictionsForRouteStopDest	Contains list of predictions for a route/stop/destination.
IpcRoute	Describes a route such that it can e displayed in a UI.
IpcRouteSummary	Contains configuration information for a single route.
IpcSchedTime	A schedule time for a particular stop/trip.
IpcSchedTimes	Configuration information for a schedule times for IPC.
IpcSchedTrip	For describing a trip as part of a schedule
IpcSchedule	Used by RMI to transfer data for a schedule for a route/direction/service
IpcServerStatus	Represents server status for Inter Process Communication (IPC)
IpcShape	Represents a shape for Inter Process Communication (IPC)
IpcStop	Contains information for a single route.
IpcStopPath	Configuration information for a StopPath for IPC.
IpcTrip	Configuration information for a Trip for IPC.
IpcTripPattern	Configuration information for a TripPattern.
IpcVehicle	Contains information on a single vehicle.
IpcVehicleComplete	Extension of IpcVehicle class so that all info describing vehicle is included.
IpcVehicleConfig	For transmitting via Interprocess Communication vehicle configuration info.
IpcVehicleGtfsRealtime	Extension of IpcVehicle class so that additional info can be provided for GTFS-realtime feed.

Enum Summary

Enum	Description
IpcPrediction.ArrivalOrDeparture

Package org.transitime.ipc.data Description

This package contains the low-level objects that are transmitted to the clients via RMI.

There are many goals with these objects:

• Objects should be Immutable so that they are always coherent and threadsafe.
• Objects must be serializable so can be used with RMI.
• Have a version number for the class so that can handle objects of different versions. This is key because won't always be able to update the servers and clients at same time.

The way to achieve the goals is to use a inner "SerializationProxy" class as described by Joshua Bloch in "Effective Java 2nd Edition" in item 78. See the org.transitime.ipc.data.Vehicle class for an example. Yes, this is more complicated then using the default serialization but the default is simply not adequate because some of the structures will change over time and the default serialization cannot handle all such changes.

Author:

SkiBu Smith