Connection architecture for a mobile network

1. A server that manages transactions between first and second 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 from a first device;

authenticate the first device over the first connection;

receive a first transaction from the first device in response to user input at the first device, wherein the first connection is maintained independently of the first transaction;

generate a trigger for a second device based on the first transaction from the first device, wherein the trigger is pushed to the second device;

after the generation of the trigger for the second device, receive a second connection from the second device while the first connection is maintained;

authenticate the second device over the second connection,

wherein the trigger notifies the second device of new data from the first transaction to be received by the second device from the server for display to a user; and

send a second transaction to the second device using the second connection, wherein the second transaction contains the new data,

wherein the trigger is pushed over a connection different from the second connection,

wherein a third transaction is received by the server in response to user input at the second device.

2. The server of claim 1 , wherein the first device is in a private network that contains a firewall.

3. The server of claim 2 , wherein the server is in a publicly accessible network.

4. The server of claim 1 , wherein the second device is in a wireless network.

5. The server of claim 1 , wherein the server is further operable to:

receive configuration information from the first device, wherein the configuration information comprises login data associated with a user of the first device.

6. The server of claim 1 , wherein the first transaction includes data selected from the group comprising: electronic messages, calendar data, contact information data, task data, note data, documents, and files.

7. The server of claim 6 , wherein the electronic messages comprise electronic mail (email) data.

8. The server of claim 1 , wherein the trigger contains information that causes the second connection to be received by the server.

9. The server of claim 1 , wherein the second connection is received in response to user input received at the second device.

10. The server of claim 1 , wherein the server is further configure to:

send the trigger to the second device via a Short Message Service Center.

11. The server of claim 1 , wherein the server is further operable to:

generate a third trigger for a third device based on the first transaction; and

receive a third connection from the third device.

12. The server of claim 11 wherein the server is further operable to:

send a third transaction to the third device using the third connection.

13. The server of claim 12 , wherein the third transaction contains data from the first transaction.

14. The server of claim 1 , wherein the second transaction contains data from the first transaction.

15. The server of claim 1 , wherein maintaining the first connection with the first device independently of the first transaction comprises automatically reestablishing the first connection with the first device if the first connection is disconnected for any reason.

16. The server of claim 1 , wherein the server is further operable to:

terminate the first connection.

17. The server of claim 1 , wherein the server is operable to: receive a message from the first device, wherein receipt of the message terminates the first connection.

18. The server of claim 1 , wherein the server is further operable to:

terminate the second connection.

19. The server of claim 1 , wherein the server is further operable to:

receive a message from the second device terminating the second connection.

20. A method of operating a server to manage transactions between first and second devices, the method comprising: receiving a first connection from a first device;

authenticating the first device over the first connection;

receiving a first transaction from the first device in response to user input at the first device, wherein the first connection is maintained independently of the first transaction;

generating a trigger for a second device based on the first transaction from the first device, wherein the trigger notifies the second device of new data from the first transaction to be received by the second device from the server for display to a user, wherein the trigger is pushed to the second device;

after the generation of the trigger for the second device, receiving a second connection from the second device while the first connection is maintained;

authenticating the second device over the second connection; and

sending a second transaction to the second device using the second connection, wherein the second transaction contains the new data,

wherein the trigger is pushed over a connection different from the second connection,

wherein a third transaction is received by the server in response to user input at the second device.

21. The method of claim 20 , wherein the first device is in a private network that contains a firewall.

22. The method of claim 21 , wherein the server is in a publicly accessible network.

23. The method of claim 20 , wherein the second device is in a wireless network.

24. The method of claim 20 , the method further comprising:

receiving configuration information from the first device, wherein the configuration information comprises login data associated with a user of the first device.

25. The method of claim 20 , wherein the first transaction includes data selected from the group comprising: electronic messages, calendar data, contact information data, task data, note data, documents, and files.

26. The method of claim 25 , wherein the electronic messages comprise electronic mail (email) data.

27. The method of claim 20 , wherein the trigger notifies the second device of new data to be received by the second device from the server.

28. The method of claim 20 , wherein the trigger contains information that causes the second connection to be received by the server.

29. The method of claim 20 , wherein the second connection is received in response to user input received at the second device.

30. The method of claim 20 , the method further comprising:

sending the trigger to the second device via a Short Message Service Center.

31. The method of claim 20 , the method further comprising:

generating a third trigger for a third device based on the first transaction;

receiving a third connection from the third device.

32. The method of claim 31 , the method further comprising: Sending a fourth transaction to the third device using the third transaction.

33. The method of claim 20 , wherein the second transaction contains data from the first transaction.

34. The method of claim 20 , wherein maintaining the first connection with the first device independently of the first transaction comprises automatically reestablishing the first connection with the first device if the first connection is disconnected for any reason.

35. The method of claim 20 , the method further comprising:

terminating the first connection.

36. The method of claim 20 , the method further comprising: Receiving a message from the first device, wherein the receipt of the message terminates the first transaction.

37. The method of claim 20 , the method further comprising:

terminating the second connection.

38. The method of claim 20 , the method further comprising:

receiving a message from the second device terminating the second connection.