System and server for managing communications between end user devices

1. A server that manages transactions between first and second end user devices, the server comprising:

a communication interface;

a processor communicatively coupled to the communication interface; and

a memory communicatively coupled to the processor, the memory containing instructions executable by the processor whereby the server is operable to:

receive a first connection associated with a first end user device, wherein the first connection includes a connection that is initiated by the first end user device, and wherein the first end user device is authenticated by matching information in an authentication token presented by the first end user device with previously stored information;

receive a first message from the first end user device over the first connection, wherein the first connection is maintained independently of the first message, and wherein the first message is associated with a transaction requesting data from a second end user device;

generate a second message for the second end user device based on the first message from the first end user device;

send the second message to the second end user device;

receive a second connection associated with the second end user device while the first connection is maintained,

wherein the second connection includes a connection that is initiated by the second end user device;

receive a third message from the second end user device over the second connection,

wherein the third message is generated by the second end user device in response to receipt of the second message, and

wherein the third message contains a latest version of data from the second end user device;

generate a fourth message, wherein the fourth message includes data from the third message; and

send the fourth message to the first end user device over the first connection;

wherein stateless connectivity exists between the first end user device and the second end user device over the first connection and the second connection.

2. The server of claim 1 , wherein the second connection is used to manage multiple transactions between the first end user device and the second end user device.

3. The server of claim 2 , wherein the multiple transactions between the first end user device and the second end user device are managed in response to instructions from a user of the first end user device.

4. The server of claim 2 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes a request to receive additional data from the first end user device.

5. The server of claim 2 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes a request to receive additional data from a third device.

6. The server of claim 2 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes additional data for receipt by a third device.

7. The server of claim 2 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes additional data for receipt by the first end user device.

8. The server of claim 1 , wherein the second message includes data from the first message.

9. The server of claim 1 , wherein the server is operable to receive a third connection associated with the second end user device after the second message is sent to the second end user device.

10. The server of claim 9 , wherein the server is operable to manage transactions between the first end user device and the second end user device over the first and third connection.

11. The server of claim 1 , wherein the first connection is a TCP/IP connection.

12. The server of claim 1 , wherein the server is operable to maintain the first connection regardless of whether the second connection is terminated.

13. The server of claim 1 , wherein, upon termination of the first connection or completion of the transaction, the server is operable to delete data associated with the transaction.

14. A method for managing transactions between first and second end user devices, the method comprising:

receiving, at a server, a first connection associated with a first end user device, wherein the first connection includes a connection that is initiated by the first end user device, and wherein the first end user device is authenticated by matching information in an authentication token presented by the first end user device with previously stored information;

receiving, at the server, a first message from the first end user device over the first connection, wherein the first connection is maintained independently of the first message, and wherein the first message is associated with a transaction requesting data from a second end user device;

generating, at the server, a second message for the second end user device based on the first message from the first end user device;

sending the second message from the server to the second end user device;

receiving, at the server, a second connection associated with the second end user device while the first connection is maintained,

wherein the second connection includes a connection that is initiated by the second end user device;

receiving, at the server, a third message from the second end user device over the second connection,

wherein the third message is generated by the second end user device in response to receipt of the second message, and

wherein the third message contains a latest version of data from the second end user device;

generating, at the server, a fourth message, wherein the fourth message includes data from the third message; and

sending the fourth message from the server to the first end user device over the first connection;

wherein stateless connectivity exists between the first end user device and the second end user device over the first connection and the second connection.

15. The method of claim 14 , wherein the second connection is used to manage multiple transactions between the first end user device and the second end user device.

16. The method of claim 14 , wherein the second message includes data from the first message.

17. The method of claim 15 , wherein the multiple transactions between the first end user device and the second end user device are managed in response to instructions from a user of the first end user device.

18. The method of claim 15 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes a request to receive additional data from the first end user device.

19. The method of claim 15 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes a request to receive additional data from a third device.

20. The method of claim 15 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes additional data for receipt by a third device.

21. The method of claim 15 , wherein at least one of the multiple transactions between the first end user device and the second end user device includes additional data for receipt by the first end user device.

22. The method of claim 14 , further comprising receiving, at the server, a third connection associated with the second end user device after the second message is sent to the second end user device.

23. The method of claim 22 , further comprising managing, by the server, transactions between the first end user device and the second end user device over the first and third connection.

24. The method of claim 14 , wherein the first connection is a TCP/IP connection.

25. The method of claim 14 , further comprising maintaining the first connection regardless of whether the second connection is terminated.

26. The method of claim 14 , further comprising deleting data associated with the transaction upon termination of the first connection or completion of the transaction.