System and method for providing a protocol for message data

1. A system for accessing messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the message information for each message specifying an intended receiving client device, the system comprising:

a message server coupled to the message storage system and configured for:

retrieving message data from the message storage system and sending the message data to a receiving client device through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message, the message information for the at least one message specifying the receiving client device as the intended receiving client device; and

a user interface (UI) server configured for:

sending UI data to the receiving client device through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data, the UI data for producing webpages of the client UI on the receiving client device, the message data for populating the webpages of the client UI, the message server and the UI server being different servers, the message server and UI server being simultaneously coupled to the receiving client device, wherein the message server sends message data through the first network connection to the receiving client device while the UI server simultaneously sends UI data through the second network connection to the receiving client device, wherein the message data comprises no UI data, the UI data comprises no message data, the message server does not send UI data to the receiving client device, and the UI server does not send message data to the receiving client device.

2. The system of claim 1 , wherein the message server is further configured for:

sending a message list of current messages to the receiving client device at a beginning of a message session with the receiving client device; and

during the message session, sending a notification of a new message or call to the receiving client device without receiving a request for data from the receiving client device, wherein the new message or call is not represented in the message list.

3. The system of claim 2 , wherein:

the message session ends at an approximate point in time that the message server receives a session-end request from the receiving client device; and

during the message session, the message server automatically sends the notification of the new message or call upon receiving the new message or call.

4. The system of claim 1 , wherein the message server sends only message data through the first network connection to the receiving client device during a same or overlapping timeframe that the UI server sends only UI data through the second network connection to the receiving client device.

5. The system of claim 1 , wherein:

the message server sends message data to the receiving client device through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type; and

the message server is further configured for sending message data to the receiving client device through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

6. The system of claim 1 , wherein the non-HyperText Transfer Protocol comprises jWebSocket protocol.

7. The system of claim 1 , wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

8. A non-transitory computer readable medium having instructions stored thereon when executed by a processor, accesses messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the message information for each message specifying an intended receiving client device, the non-transitory computer readable medium comprising instructions for:

at a message server, retrieving message data from the message storage system and sending the message data to a receiving client device through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message, the message information for the at least one message specifying the receiving client device as the intended receiving client device; and

at a user interface (UI) server, sending UI data to the receiving client device through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data, the UI data for producing webpages of the client UI on the receiving client device, the message data for populating the webpages of the client UI, the message server and the UI server being different servers, the message server and UI server being simultaneously coupled to the receiving client device, wherein the message server sends message data through the first network connection to the receiving client device while the UI server simultaneously sends UI data through the second network connection to the receiving client device, wherein the message data comprises no UI data, the UI data comprises no message data, the message server does not send UI data to the receiving client device, and the UI server does not send message data to the receiving client device.

9. The non-transitory computer readable medium of claim 8 , further comprising instructions for:

at the message server:

sending a message list of current messages to the receiving client device at a beginning of a message session with the receiving client device; and

during the message session, sending a notification of a new message or call to the receiving client device without receiving a request for data from the receiving client device, wherein the new message or call is not represented in the message list.

10. The non-transitory computer readable medium of claim 9 , wherein:

the message session ends at an approximate point in time that the message server receives a session-end request from the receiving client device; and

during the message session, the message server automatically sends the notification of the new message or call upon receiving the new message or call.

11. The non-transitory computer readable medium of claim 8 , wherein the message server sends only message data through the first network connection to the receiving client device during a same or overlapping timeframe that the UI server sends only UI data through the second network connection to the receiving client device.

12. The non-transitory computer readable medium of claim 8 , wherein the message server sends message data to the receiving client device through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type, the non-transitory computer readable medium further comprising instructions for:

at the message server, sending message data to the receiving client device through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

13. The non-transitory computer readable medium of claim 8 , wherein the non-HyperText Transfer Protocol comprises jWebSocket protocol.

14. The non-transitory computer readable medium of claim 8 , wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

15. A system for accessing messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the message information for each message specifying an intended receiving client device, the system comprising:

a receiving client device configured for:

receiving message data from a message server through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message, the message information for the at least one message specifying the receiving client device as the intended receiving client device;

receiving user interface (UI) data from a UI server through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data;

using the UI data for producing webpages of the client UI on the receiving client device; and

using the message data for populating the webpages of the client UI, the message server and the UI server being different servers, the receiving client device being simultaneously coupled to the message server and UI server, wherein the receiving client device receives message data from the message server through the first network connection while simultaneously receiving UI data from the UI server through the second network connection, wherein the message data comprises no UI data, the UI data comprises no message data, the message server does not send UI data to the receiving client device, and the UI server does not send message data to the receiving client device.

16. The system of claim 15 , wherein the receiving client device receives message data through the first network connection during a same or overlapping timeframe as receiving UI data through the second network connection.

17. The system of claim 15 , wherein the receiving client device, in parallel, receives and processes message data through the first network connection and UI data through the second network connection.

18. The system of claim 15 , wherein:

the receiving client device receives message data from the message server through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type; and

the receiving client device is further configured for receiving message data from the message server through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

19. The system of claim 15 , wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

20. The system of claim 15 , wherein:

the receiving client device comprises a JavaScript engine and message data communicator engine; and

the JavaScript engine requests the message data from the message data communicator engine which submits the request to the message server for requesting the message data.

21. A non-transitory computer readable medium having instructions stored thereon when executed by a processor, accesses messages on a message storage system configured for receiving a plurality of messages through a network connection system from a plurality of sending client devices and storing the messages and message information associated with the messages, the message information for each message specifying an intended receiving client device, the non-transitory computer readable medium comprising instructions for:

at a receiving client device:

receiving message data from a message server through a first network connection using a non-HyperText Transfer Protocol, the message data comprising at least one message and message information associated with the at least one message, the message information for the at least one message specifying the receiving client device as the intended receiving client device;

receiving user interface (UI) data from a UI server through a second network connection using a HyperText Transfer Protocol, the receiving client device comprising a web browser comprising a client UI for accessing message data;

using the UI data for producing webpages of the client UI on the receiving client device; and

using the message data for populating the webpages of the client UI, the message server and the UI server being different servers, the receiving client device being simultaneously coupled to the message server and UI server, wherein the receiving client device receives message data from the message server through the first network connection while simultaneously receiving UI data from the UI server through the second network connection, wherein the message data comprises no UI data, the UI data comprises no message data, the message server does not send UI data to the receiving client device, and the UI server does not send message data to the receiving client device.

22. The non-transitory computer readable medium of claim 21 , wherein the receiving client device receives message data through the first network connection during a same or overlapping timeframe as receiving UI data through the second network connection.

23. The non-transitory computer readable medium of claim 21 , wherein the receiving client device, in parallel, receives and processes message data through the first network connection and UI data through the second network connection.

24. The non-transitory computer readable medium of claim 21 , wherein the receiving client device receives message data from the message server through the first network connection using a first non-HyperText Transfer Protocol, the message data comprising a first message type, the non-transitory computer readable medium further comprising instructions for:

at the receiving client device, receiving message data from the message server through a third network connection using a second non-HyperText Transfer Protocol, the message data comprising a second message type, the first and second non-HyperText Transfer Protocols being different non-HyperText Transfer Protocols and the first and second message types being different message types.

25. The non-transitory computer readable medium of claim 21 , wherein:

the client UI comprises a hyper-text mark-up language (HTML) UI; and

the UI data comprises HTML formatted text, graphics, tables, or selectable icons for producing webpages for the HTML UI.

26. The non-transitory computer readable medium of claim 21 , wherein:

the receiving client device comprises a JavaScript engine and message data communicator engine; and

the JavaScript engine requests the message data from the message data communicator engine which submits the request to the message server for requesting the message data.