CALIFORNIA SOFTWARE LABS

Transcription

1 Using the JetSend SDK CALIFORNIA SOFTWARE LABS R E A L I Z E Y O U R I D E A S California Software Labs 6800 Koll Center Parkway, Suite 100 Pleasanton CA 94566, USA. Phone (925) Fax (925) info@cswl.com

2 Using the JetSend SDK A Technical Report Technical Expertise Level : Intermediate Requires knowledge of : JetSend Protocol Shelf Life : 6-8 months INDEX INTRODUCTION... 3 INITIALIZE THE JETSEND STACK AND CLIENT MANAGER... 3 LOOP AND PROCESS EVENTS... 4 SHUTDOWN JETSEND... 4 CONTROL FLOWS IN JETSEND SDK APPLIANCES... 4 CSWL Inc, Pleasanton, California - 2 -

3 Introduction This part discusses in detail, the various steps involved in integrating the JetSend SDK with the device code. Initialize the JetSend Stack and client Manager. Loop and Process events. Shutdown the JetSend Stack. Initialize the JetSend Stack and Client Manager This involves Activity Manager Initialize A call to an API named aminitializeforwindows () should be made for initializing the activity manager queues for events and memory locations used. The device should have been registered with the Client Manager before calling aminitializeforwindows (). Client Manager Initialize This should be done to initialize the client manager to perform operations like registration and de-registration of devices, querying for specific devices, enabling/disabling specific devices etc. A call to an API named jscminitialize () initializes the Client Manager. Support Modules Initialize A device depending on its role, Sender or Receiver uses one or more support modules in the activity Layer. A sending device will use the Push send module and CSWL Inc, Pleasanton, California - 3 -

4 hence it must be initialized. Any additional modules used by it like Status Receive, Address receive, or Contact module must also be initialized. Similarly a Receiving device must initialize the Push receive module followed by the initialization of any additional modules it uses. Loop and Process events The core initialization makes the JetSend core ready for activities. The device should then repeatedly query for events through its main loop. A call to check for the next event is made, if the call returns NULL, the event is ignored else the function implementing the action for the corresponding event is called. Shutdown JetSend In this shutdown sequence the function calls are in the exact reverse order of the function calls for initialization. First the various support modules used are shutdown, followed by the activity manager shutdown, the Client Manager shut down and finally the JetSend stack shutdown Control flows in JetSend SDK appliances As said earlier, the program flow between a JetSend SDK sender and a receiver appliance is almost the same except for the usage of a few support modules. SDK sender appliances use the Push send module whereas SDK receiver appliances use the push receive modules. CSWL Inc, Pleasanton, California - 4 -

5 Control Flow in a Sender appliance This can be explained as follows. Start the Sender and get the Receiver's JMN and the image to be sent. Start a JetSend's main thread, which performs the main event handling part of the loop. In this thread do the following o Initialize the Activity Manager, the Client Manager, the Contact Manager, the status and the push sender modules. o In a while loop keep checking for any event occurrence by calling GetAndProcessEvent method. CSWL Inc, Pleasanton, California - 5 -

6 o If any event occurs GetAndProcessEvent transfers control to CEventSupport's method ProcessEvent, which will process the event type and call its corresponding event handler. Here the Event handlers are available in CImageSenderImpl class. while (!bshutdownjetsend) { if (pjetsend->getandprocessevent() ) } Once this bshutdownevent becomes true it comes out of the loop and shuts down the JetSend system by calling ShutDownJetSend and TerminateJetSend. Shutdown the application with JetSendShutDown which will call psshutdown (push sender shutdown), srshutdown (status module shutdown), conshutdown (Contact Manager shutdown) and finally amshutdown (). This ensures that the JetSend system is shut down properly. CSWL Inc, Pleasanton, California - 6 -

7 Control Flow in a Receiver The control flow for a receiver is very much the same except for the initialization and shut down of the push receive module. The rest of the things are the same as we have in the sender appliance Copyright Notice: 2002 California Software Labs. All rights Reserved. The contents on the document are not to be reproduced or duplicated in any form or kind, either in part or full, without the written permission of California Software labs. Product and company names mentioned here in are the trademarks of their respective companies. CSWL Inc, Pleasanton, California - 7 -