Inline media

Abstract

Systems and methods providing users with a rich web experience are disclosed. In one embodiment, a client and at least one server are in communication using a dual communication link. In another embodiment, a markup language based instant messaging application is disclosed. The instant messaging application may include group instant messaging. The instant messaging application may also provide group member persistence and message persistence at the server. In another embodiment, a card based web application is disclosed, where the card information and character may be shared with other users or within a group. The cards may also be configurable by users.

What is claimed is: 
     
         1 . A system comprising:
 one or more processors:   one or more machine-readable media storing instructions which, when executed by the one or more processors, cause:
 establishing a first connection between a server and a first client; 
 establishing a second connection between the server and the first client, wherein the second connection is different than the first connection; 
 sending first data from the server through the first connection to the first client; 
 receiving, at the server, second data from a second client that is different than the first client; 
 adding, at the server, the second data to the first data to create third data; 
 maintaining the third data at the server; 
 after sending the first data through the first connection to the first client, sending, from the server through the second connection to the first client, the second data that is associated with the first data; 
 storing a group list that identifies a plurality of clients, that includes the first client and the second client, as members of a particular group; 
 after storing the group list and after sending the second data to the first client, determining, by the server, that a third client becomes a member of the particular group, wherein the third client is different than the first client and the second client; 
 in response to determining that the third client becomes a member of the particular group, sending, by the server, the third data to the third client. 
   
     
     
         2 . The system of  claim 1 , wherein the instructions, when executed by the one or more processors, further cause:
 receiving, at the server through the first connection from the first client, a request for the first data;   wherein sending the first data comprises sending the first data to the first client in response to receiving the request.   
     
     
         3 . The system of  claim 1 , wherein the instructions, when executed by the one or more processors, further cause:
 in response to receiving the second data from the second client, sending the second data to other members of the particular group.   
     
     
         4 . The system of  claim 1 , wherein the first connection is a different type of connection than the second connection. 
     
     
         5 . The system of  claim 1 , wherein the first connection is an HTTP connection and the second connection is an XMPP connection or a JABBER connection. 
     
     
         6 . The system of  claim 1 , wherein:
 the server includes a first server and a second server that is different than the first server;   the first connection is between the first client and the first server;   the second connection is between the first client and the second server.   
     
     
         7 . The system of  claim 1 , wherein the instructions, when executed by the one or more processors, further cause:
 receiving, from a particular client, at the server, a request for a data file;   in response to receiving the request, sending the data file to the particular client;   receiving, from the particular client, at the server, a marked up version of a message that was created at the particular client based on user input;   storing, by the server, the marked up version of the message within the data file.   
     
     
         8 . A method comprising:
 establishing a first connection between a server and a first client;   establishing a second connection between the server and the first client, wherein the second connection is different than the first connection;   sending first data from the server through the first connection to the first client;   receiving, at the server, second data from a second client that is different than the first client;   adding, at the server, the second data to the first data to create third data;   maintaining the third data at the server;   after sending the first data through the first connection to the first client, sending, from the server through the second connection to the first client, the second data that is associated with the first data;   storing a group list that identifies a plurality of clients, that includes the first client and the second client, as members of a particular group;   after storing the group list and after sending the second data to the first client, determining, by the server, that a third client becomes a member of the particular group, wherein the third client is different than the first client and the second client;   in response to determining that the third client becomes a member of the particular group, sending the third data to the third client;   wherein the method is performed by one or more computing devices.   
     
     
         9 . The method of  claim 8 , further comprising:
 receiving, at the server through the first connection from the first client, a request for the first data;   wherein sending the first data comprises sending the first data to the first client in response to receiving the request.   
     
     
         10 . The method of  claim 8 , further comprising:
 in response to receiving the second data from the second client, sending the second data to other members of the particular group.   
     
     
         11 . The method of  claim 8 , wherein the first connection is a different type of connection than the second connection. 
     
     
         12 . The method of  claim 8 , wherein the first connection is an HTTP connection and the second connection is an XMPP connection or a JABBER connection. 
     
     
         13 . The method of  claim 8 , wherein:
 the server includes a first server and a second server that is different than the first server;   the first connection is between the first client and the first server;   the second connection is between the first client and the second server.   
     
     
         14 . The method of  claim 8 , further comprising:
 receiving, from a particular client, at the server, a request for a data file;   in response to receiving the request, sending the data file to the particular client;   receiving, from the particular client, at the server, a marked up version of a message that was created at the particular client based on user input;   storing, by the server, the marked up version of the message within the data file.