IP Library Granted Patent US 7,199,885
Granted Patent B2
US 7,199,885 · App. 10/986,779 · Granted Apr 3, 2007

Generic interface

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,199,885
App. No.
10/986,779
Granted
Apr 3, 2007
Kind
B2
Abstract

A system and process for ensuring the smooth flow of electronic ink is described. Dynamic rendering is give priority over other event handlers. Priority may be the use of one or more queues to order when events occur and may be performing dynamic rendering prior to other steps.

Claims (50)

1. A method for communicating between a component and plug-in objects, said component including a synchronous interface and an asynchronous interface, said method comprising the steps of:

receiving a data packet at said component;

placing said data packet at a location;

notifying a list of plug-in objects to the existence of said data packet;

processing said data packet through said list of plug-in objects using said synchronous interface;

receiving said data packet from said list of plug-in objects;

placing said data packet in an output queue of said component;

notifying a second list of plug-in objects to the existence of said data packet; and

processing said data packet through said second list of plug-in objects through said asynchronous interface.

2. A method for relating plug-in objects to a component comprising the steps of:

forming a first list that may contain a reference to plug-in objects;

attaching said first list to a synchronous interface of said component;

populating said first list with references to at least one plug-in object,

forming a second list that may contain a reference to plug in objects;

attaching said second list to an asynchronous interface of said component; and

populating said second list with references to at least one plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first list, and

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second list attached to said asynchronous interface.

3. A method for relating plug-in objects to a component comprising the steps of:

attaching a first plug-in object to a synchronous interface on said component; and

attaching a second plug-in object to a synchronous interface on said first plug-in object to form a first chain linking said component, said first plug-in object, and said second plug-in object;

attaching a third plug-in object to an asynchronous interface on said component; and

attaching a fourth plug-in object to an asynchronous interface on said third plug-in object to form a second chain linking said component, said third plug-in object, and said fourth plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first chain,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second chain.

4. A system for communicating between a component and plug-in objects, said component having a synchronous interface and an asynchronous interface, said system comprising:

means for receiving a data packet at said component;

means for placing said data packet at a location;

means for notifying a list of plug-in objects to the existence of said data packet;

means for processing said data packet through said list of plug-in objects using said synchronous interface;

means for receiving said data packet from said list of plug-in objects;

means for placing said data packet in an output queue of said component;

means for notifying a second list of plug-in objects to the existence of said data packet; and

means for processing said data packet through said second list of plug-in objects through said asynchronous interface.

5. A system for relating plug-in objects to a component, said component including a synchronous interface and an asynchronous interface, said system comprising:

means for forming a first list that may contain a reference to plug-in objects;

means for attaching said first list to a synchronous interface of said component;

means for populating said first list with references to at least one plug-in object;

means for forming a second list that may contain a reference to plug-in objects;

means for attaching said second list to said asynchronous interface of said component; and

means for populating said second list with references to at least one plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first list, and

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second list attached to said asynchronous interface.

6. A system for relating plug-in objects to a component, said component including a synchronous interface and an asynchronous interface, said system comprising:

means for attaching a first plug-in object to an interface on said component;

means for attaching a second plug-in object to an interface on said first plug-in object to form a first chain linking said component, said first plug-in object, and said second plug-in object;

means for attaching a third plug-in object to said asynchronous interface on said component; and

means for attaching a fourth plug-in object to an asynchronous interface on said third plug-in object to form a chain linking said component, said third plug-in object, and said fourth plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first chain, and

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second chain.

Assignments (3)
CORRECTIVE ASSIGNMENT TO CORRECT THE RECORDAL TO REMOVE INADVERTENTLY RECOREDED PROPERTIES SHOWN IN ATTACHED SHEET PREVIOUSLY RECORDED AT REEL: 047681 FRAME: 0916. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 18, 2019
From: MICROSOFT TECHNOLOGY LICENSING, LLC
To: SERVICENOW, INC.
Reel/Frame 049797/0119 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 29, 2018
From: MICROSOFT TECHNOLOGY LICENSING, LLC
To: SERVICENOW, INC.
Reel/Frame 047681/0916 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2014
From: MICROSOFT CORPORATION
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 034543/0001 →