Optimising client attachment into a distributed bus using standard interfaces
Original Publication Date: 2005-Jan-20
Included in the Prior Art Database: 2005-Jan-20
In a Java* Message Service or similar system, different resources may be hosted on different engines within a 'bus' of connected engines. Destinations are accessible via connections to any engine on the bus, but most efficiently accessed via connection to the hosting engine. The initial connection may only specify the bus. The proposal is to defer connection until at least one destination access is made; giving the application code a 'pending' connection. By the time destination access is required the system has knowledge of where that destination is hosted (and other destinations already referenced in the program but not yet accessed). The system uses this information to decide the best engine within the bus for connection, and makes a real connection to that bus based on that information. Typically, that will be a connection to the engine; but other connections may be used, eg if that engine is not accepting connections. This has the benefit that better connection decisions may be made, without requiring changes to the application program. The application program is not aware of the change from 'pending' to 'real' connection.