Browse Prior Art Database

Trigger server for networked applications

IP.com Disclosure Number: IPCOM000010304D
Original Publication Date: 2002-Nov-19
Included in the Prior Art Database: 2002-Nov-19
Document File: 1 page(s) / 39K

Publishing Venue

IBM

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 81% of the total text.

Page 1 of 1

Trigger server for networked applications

    A Trigger Server is a centralized component that is used to isolate application specific pieces of logic into a componentized network consumable event (Trigger). An application has the need to publish its logical definitions of work. By introducing the component herein referred to as a Trigger Server, an application can easily accomplish this task.

Step 1: Application requests Trigger Server to create a Trigger object. The application includes its callback logic in the request. Step 2: The Trigger Server's factory creates a Trigger object and stores it in an internal repository. This Trigger object contains the application callback logic and a mechanism for creating protocol specific URLs based on the protocols supported by the Trigger Server. Then an instance of the Trigger object is returned to the application. Step 3: The application can then publish the Trigger to networked consumers such as directories, databases, web services, or client devices. Step 4: Trigger URL delivered to client devices through standard content delivery such as HTML or WML. Step 5: End user navigates to the URL Step 6: Request is received by protocol specific Trigger Listener Step 7: Listener executes callback logic associated with Trigger

The use of a Trigger Server has two major advantages:
1.) The application that creates a trigger does not need to be accessible when the trigger is activated.
2.) The application doesn't need to be concerned w...