Abstract: An event architecture facilitates the asynchronous invocation of events at an event sink. The events are triggered by direct invocation of methods on the event sink. A backchannel connection may be utilized to pass control information from an event sink to an event source. The use of the backchannel connection creates bidirectional connections between an event source and an event sink. A guardian object may be situated between the event source and the event sink to facilitate the asynchronicity of event delivery and to account for disparate threading models between the event source and the event sink. A third party connector may be utilized to connect the event source with the event sink.

Abstract: A hypermedia-based navigation system includes a plurality of information providers and one or more clients. Databases of available hyperlink targets are maintained by the information providers. Each of the databases is searchable by means of one or more query attributes supported by the database and relating to the available hyperlink targets. A hypermedia document might contain a soft hyperlink, consisting of a query formulation specified in terms of query attributes and of values for said query attributes. A client resolves a soft hyperlink by querying at least one of the databases with the query formulation to locate one or more hyperlink targets having attributes and attribute values that satisfy the query formulation. The soft hyperlink can additionally contain executable rules. The client executes these rules prior to submitting the query formulation to the database. Each rule, when it executes, potentially adds search predicates to the original query formulation.

Abstract: An event architecture facilitates the asynchronous invocation of events at an event sink. The events are triggered by direct invocation of methods on the event sink. A backchannel connection may be utilized to pass control information from an event sink to an event source. The use of the backchannel connection creates bidirectional connections between an event source and an event sink. A guardian object may be situated between the event source and the event sink to facilitate the asynchronicity of event delivery and to account for disparate threading models between the event source and the event sink. A third party connector may be utilized to connect the event source with the event sink.