Method and apparatus to select and deliver portable portlets

• US 9,071,570 B2
• Filed: 03/30/2005
• Issued: 06/30/2015
• Est. Priority Date: 03/30/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Etgen, Michael Peter, Fox, James Edward, Miller, Steven Michael
• Primary Examiner(s): Zele, Krista
• Assistant Examiner(s): LINDSEY, MATTHEW S
• Application Number:
  US11/094,092
• Publication Number:
  US 20060230059A1
• Time in Patent Office: 3,744 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions

Abstract

A portlet may be selected from among one or more portlets rendered by an origin server. The origin server may have an object listening for pointer activity wherein a user event triggers selection of a portlet. The origin server, in response, may send state information of the portlet in the form of a key to a client, often operated by a user. Client may later send the key to a disjoint server, wherein the key is integrated into a portal containing services that the client subscribes to. Thus a persistent session may exist between the disjoint server and the origin server based on the user'"'"'s preferences.

Claims

1. A method to selectively move a portlet among portals, the portlet having a portlet state including portlet session information, comprising the steps of:

receiving Hypertext Transfer Protocol (HTTP) request at an originating server from a client;

rendering a portlet by the originating server in a first portal at the client responsive to receiving the HTTP request, the portlet having a decoration provided by the originating server and an event trigger associated with the decoration, the decoration coupled to a servlet;

receiving a first user event at the originating server, the first user event corresponding to the event trigger, wherein receiving the first user event comprises receiving a drag indication, and wherein receiving the drag indication comprises receiving the drag indication at coordinates within a portlet window;

receiving a second user event at the originating server that includes a drop indication, wherein receiving the second user event at the originating server includes receiving a pointer action;

serializing the portlet state based on the first user event at the originating server, performed by the servlet;

storing the portlet state in a key at the originating server by the servlet, wherein storing the portlet state includes storing a uniform resource identifier in the key; and

sending the key having the portlet state to the client from the originating server, wherein the key is configured to allow a disjoint server to render the portlet in a second portal rendered at the client and provided by the disjoint server to the client, the disjoint server operating in a different administrative domain than the originating server;

wherein the first and second portals are displayed in first and second browser windows at the client.

2. An originating server for selecting a portlet, the portlet having a portlet state including portlet session information, comprising:

a processor for rendering the portlet in a first portal in a first browser window at a client, the portlet having a decoration and an event trigger associated with the decoration, the decoration provided by the originating server and coupled to a servlet;

a network adapter at the originating server for receiving a first user event at the originating server, the first user even corresponding to the event trigger, the network adapter coupled to the processor, wherein the network adapter comprises means for receiving a drag indication, and wherein the means for receiving the drag indication comprises means for receiving the drag indication at coordinates within a portlet window;

the network adapter receives a second user event at the originating server that includes a drop indication, wherein the second user event includes a pointer action indicating the drop indication at a second portal provided by a disjoint server;

a means for serializing the portlet state at the originating server by the servlet based on the first user event, the means to serialize coupled to the processor;

a memory to store the portlet state in a key at the originating server, wherein the memory stores a uniform resource identifier in the key, and wherein the key is configured to allow the disjoint server to render the portlet in the second portal in a second browser window at the client, the disjoint server operating in a different administrative domain from the originating server;

a LAN adapter to send the key having the portlet state to a client; and

a means for billing the client operatively coupled to the processor.

3. A method of transferring a portlet from a first portal rendered at a client, the first portal provided by an origin server, to a second portal rendered at the client, the second portal provided by a disjoint server operating in a different administrative domain from the origin server, comprising:

rendering, at the client, the first portal in a first browser window on a display of the client in response to portal code received from the origin server;

rendering, at the client, the portlet in the first portal, including a decoration on the portlet provided by the origin server, the decoration having an event trigger;

rendering, at the client, the second portal in a second browser window on the display;

detecting a first event at the decoration via the event trigger, the event being an input associated with the decoration from a user of the client;

in response to detecting the event, transmitting a request to the origin server;

receiving from the origin server at the client a key, the key containing state information of the portlet including a portlet session identifier and identification of the client, the origin server, and the disjoint server;

detecting in the second portal a second event;

in response to detecting the second event, transmitting the key to the disjoint server; and

receiving portlet code for the portlet from the disjoint server for rendering the portlet in the second portal, whereupon the portlet is rendered in the second portal with the state information.

4. The method of claim 3, wherein the key contains the state information in serialized form.

5. The method of claim 3, wherein the key contains authentication information allowing the disjoint server to authenticate the portlet with the origin server.

6. The method of claim 3, wherein the first and second events comprise a drag and drop operation.

7. The method of claim 3, wherein the key further includes a uniform resource identifier of the origin server.

8. The method of claim 3, wherein the key further includes billing information.