There are two possible basic scenarios dealing with integration patterns.

  • Sending ESME messages
  • Receiving ESME messages

Of course, there are some applications (Web Client, ESME Desktop Client, etc.) that represent both patterns but I’d like to concentrate on those applications that fulfill one pattern but not the other. 

Sending ESME Messages 

Applications that fulfill this pattern are those that supply the ESME cloud with information in the form of messages. These applications may either be based on human-created content via UI or machine-based content. Examples of this integration pattern are:

Receiving ESME Messages

Applications that fulfill this pattern are those that receive ESME messages and then process the information in some manner.. One of the main requirements for such applications are the ability to deal with long polling (ala Comet-style ) communication in order to avoid performance problems on ESME server instances. 

Possible implementations of this pattern include:

  • ESME Bots
  • Light-weight applications that just show certain messages based on tag-based filters. An integration via javascript-based scripts (for example, dojo) would allow use in most browser-based scenarios.