Currently, there are 3 main models for designing a client/server architecture with mobile clients:
1) The classic Web-like client/server design where wap or html is used in a client browser, and jsp/servlets are used on the server side to interface with an dbms using HTTP. Only the client triggers data analysis and transmission.
2) The real-time data design where the server sends data to the client without requiring that the client requests it first, commonly using TCP/IP. Both the client and the server can trigger data analysis and transmission.
3) The intermittent synchronization of batch data between a mobile and a remote component. This is mostly a batch type of data
exchange where the user or the application triggers data transmission by batches, in relatively infrequent time intervals compared to the the other two models.
Model 2 is required when the business requires that the data be pushed to the client in a semi-real-time fashion, e.g., as soon as it is available.
MIDP 1 supports Model 1 and 3, and MIDP 2 supports all 3 models. MIDP 2 supports Model 2 by using full TCP sockets between client and server, and not just HTTP connections.
[ January 14, 2004: Message edited by: serge masse ]