| Home >> All |
| • | proxy.bearer.* (11) | • | proxy.bearer.http.* (6) | • | proxy.jmsapi.* (15) | • | proxy.protocol.* (5) |
• proxy: Javadoc index of package proxy.
Package Samples:
• proxy.bearer.http
• proxy.bearer
• proxy.jmsapi
• proxy.protocol
Classes:
• ProxyRequestManager: This class provides an implementation of a thread which manages requests comming from mobile devices. The request are received in the order of their ids. The receipt protocol ensures that no request is lost and that they come in the desired order. The requests are stored in a queue and processed sequentially. For each request the appropriate action associated with this request is executed and a reply is generated. The reply is then added to the reply queue. The reply queue is emptied by the replier thread which send the replies to the mobile device using the bearer layer.
• Frame: The Frame class is an abstract class implementing a message which is sent between the library and the proxy server. The message concerns a JMS action such as creation of a new JMS object on the mobile device, a call of a JMS method on this object or a JNDI action, such as a lookup of a JMS administered object.
• Request: This class provides implementation of message sent to the proxy server. This message represents an action such as a call of a JMS or JNDI method.
• JMSObjectManager: this class object is used to store on then proxy server all JMS-specific objects that might be virtually created on the mobiles.
• JMSObjectSet: class representing a set of JMS-specific objects that are virtually created on mobiles and realy stored on the proxy server
• Reply: This class provides implementation of a reply message sent by the proxy server in reply to a request from a mobile device.
• ClientIdentifier: Informations needed to recognize single client. Consists of device number - IMEI and identifer of application running on this device
• ProxyStoredObject: abstract class representing a container which stores one real JMS specific object virtually created on some mobile.
• JNDIObject: class encapsulating object that was virtually looked up aplications on a mobiles and is stored on the proxy server
• JMSDestination: Title: Description: warstwa jmsapi do jms4j2ee Copyright: Copyright (c) 2003 Company:
• SerializeTest: Description: Tests serialization of requests in mobile.protocol and their construction i proxy.protocol
• HttpConstants: SET of constants pointing to proper value of http server response code, coresponding to http specifcation.
• JMSConsumer: class used to store an encapsulated objects of the JMS class Consumer and its subclasses
• JMSMessage: class used to store an encapsulated objects of the JMS class Message and its subclasses
• JMSConnectionFactory: class of object that stores a JMS ConnectionFactory object on the proxy server
• JMSProducer: class storing an encapsulated object of a JMS class Producer or its subclasses
• PreparedMessages: Description: This is data structere that stores messages prepared for delivery.
• PreparedMessagesTest: Title: Prepared Messages Test Suite Description: a tests suite
• JMSSession: class encapsulating object of JMS class Session or its subclasses.
• PreparedMessage: Represents three of identifer, code and jms4j2me-serialized message body
• TalkingWithMobiles: Multithread proxy server using own data structere for served data.
• ConnectionListener: Represents thread waiting for connection and serving them.
• ProxyStoredObjectType: interface containig constants used to recognise object's type
• JMSConnection: class used to store created JMSConnection objects
• Worker: Description: Threads serving http connections.
| Home | Contact Us | Privacy Policy | Terms of Service |