WO2003001767A1 - Web-enabled two-way remote messaging facility - Google Patents
Web-enabled two-way remote messaging facility Download PDFInfo
- Publication number
- WO2003001767A1 WO2003001767A1 PCT/US2002/018959 US0218959W WO03001767A1 WO 2003001767 A1 WO2003001767 A1 WO 2003001767A1 US 0218959 W US0218959 W US 0218959W WO 03001767 A1 WO03001767 A1 WO 03001767A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- event
- remote messaging
- web
- client
- server
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/564—Enhancement of application control based on intercepted application data
Definitions
- aspects of the present invention relate to World Wide Web. Other aspects of the present invention relate to messaging via World Wide Web.
- FIG. 1 is an architecture of embodiments of the present invention and the environment in which it operates.
- a web-enabled 2-way remote messaging mechanism 100 shown in Fig. 1 comprises clients 110, a server 150, and event producers 170, wherein the communication between the clients 110 and the server 150 is via a network 140a and the communication between the server 150 and the event producers 170 is via a network 140b.
- Network 140a may in general represent a communication network which may include a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, and intranet, or any other types of proprietary networks.
- Network 140b may correspond to, besides the possibilities mentioned above, an internal network. In implementation, network 140a and network 140b may also correspond to the same network.
- the clients 110 and the event producers 170 communicate via a web-enabled 2-way remote messaging mechanism facilitated by the server 150.
- the clients 110 includes one or more web clients 117,.., 132, each of which is connected to a Remote Messaging Facility (RMF) client (120,.., 135).
- the server 150 comprises a web server 155 and a Remote Messaging Facility (RMF) server 160.
- the event producers 170 includes one or more event producers 180,.., 190.
- the RMF web client 120 comprises an RMF client API 210, a session agent 212, a messaging agent 215, a message parser 217, and an event manager 220.
- the web client 117 interfaces with the RMF web client 120 through the RMF client API 210.
- the interface may allow the web client 117 to request to establish remote messaging sessions, to subscribe events, to receive notification, and to query information.
- the RMF client API 210 may also facilitate filtering operations performed on the received events using event masks. Furthermore, it may provide methods to query the content stored on the RMF server 160.
- an exemplary RMF client API is incorporated as part of the present invention.
- the RMF server 160 handles requests from the web clients, listens for events that are subscribed by web clients with respect to the message board objects, and multicasts the events to appropriate clients according to their subscriptions.
- the RMF server 160 may operate as an extension to the web server 155 as a servlet if the web server 155 supports serlet.
- the RMF server 160 may also operate as a stand-alone server connected to the web server 155 through a well-defined interface. For example, a stand- alone RMF server may interact with a web server through a Common Gateway Interface (CGI).
- CGI Common Gateway Interface
- the session manager 230 coordinates the interaction between the RMF server 160 and both the RMF web client 120 and the event producer 180.
- the session manager 230 controls RMF sessions and manages the overall process of request processing.
- An RMF_session may be considered as a trusted relationship between an RMF client and its server.
- Each session contains a unique session ID so that its client may be easily identified.
- Fig. 4 depicts a high level functional block diagram of an RMF server which shows how different parts of the RMF server 160 interact.
- the session manager 230 receives and processes the requests from the web client 117. Request processing may include invoking the message parser 240 to parse the requests. If a request corresponds to establish a remote messaging session between the web client 117 and the event producer 180, the session manager 230 may first authenticate the web client 117 through the session agent 285 located in the event producer 180. If the authentication is successful, the session manager 230 establishes a session 410 and notifies the session agent 285 of the event producer 180 that a session with the web client 117 is running.
- user authentication an authentication scheme based on user name and password pair.
- Web applications can ensure an adequate level of security by integrating a robust security framework with the web-enabled 2-way remote messaging mechanism 100 through a security agent object,
- read-only operations - a security measure which restricts a client to make any direct change to the data items stored at server side.
- a channel may connect to different listener agents.
- channel 1, 540 is connected to both listener agent 245a and 245b.
- Each channel is dedicated to a single client.
- channel 540 in Fig. 5 is dedicated to web client 1, 117.
- a web client may subscribe events that are associated with different slots in the message board 260. In this case, corresponding different listener agents are linked to the same channel to simultaneously listen to the subscribed events.
- QueryData - this command corresponds to a request to fetch the current value of a named data item stored in a message slot. If the name of the data item is omitted, the slot is, by default, a simple slot. To successfully process the request, the pre-existence of the target slot and a proper permission may be required. An error code may be returned to indicate a situation otherwise,
- PostMessage - this command corresponds to a request sent to a slot to invoke a message handler defined by an event producer.
- This request may be issued with a slot name, a message name that exists on the slot, and a list of parameters.
- a positive response may include a data item.
- a message may be posted asynchronously. In this case, the response is sent through the session's event channel.
- the commands described above may be transported over the network using an existing Internet protocol. For example, all requests may be transported from the initiating party (the web clients 110) to the web server 155 through HTTP POST.
- FIG. 6 describes exemplary schematics of a process, in which a remote messaging session is established based on a web client's request.
- the web client 117 sends a request to the session agent 212 located in the RMF web client 120 to start a session with the event producer 180.
- the messaging agent 215 encodes the BeginSession request (e.g., as HTTP POST) and sends it out to the RMF server 160.
- the session manager 230 When the session manager 230 receives the SubscribeEvent request, it examines the specified target slot in the message board 260 and contacts the filter agent 290 in the event producer to check the access rights. The session manager 230 also contacts the channel manager 235 to select one channel 420 to be dedicated to the underlying session of the request. The channel manager 235 may then initialize the dedicated channel and links the channel to an appropriate listener agent 245. The listener agent 245 monitors the subscribed event from its associated slot in the message board 260.
- Fig. 8 describes exemplary schematics of a process, in which a web client requests the RMF server 160 to listen to a subscribed event.
- the session manager 212 issues command ListenEvent and the messaging agent 215 encodes the ListenEvent command as HTTP POST and sends it out to the session manager 230 in the RMF server 160.
- the listen event request may specify the underlying session so that a channel dedicated to the session may be identified.
- the session manager 230 may verify the session and contact the channel that is dedicated to the session.
- the session manager 230 may verify the session and contact the channel that is dedicated to the session.
- the RMF web client sends a subscription request, at act 1125, to subscribe for an event with the RMF server.
- An subscription request may also be denied which is examined at act 1130. If a subscription is denied and the web client may attempt to subscribe other event, the process returns to act 1125. If there is no more events to be subscribed, determined at act 1135, the process ends at act 1140.
- the web client sends a listen request, at act 1145, the RMF server to listen to the event.
- This initiates a listening connection between the RMF web client and the RMF server.
- the subscribed event is continuously monitored at the server side.
- a subscription may be placed with respect to a certain operation performed on a particular slot in the message board. The operation may be directly related to the slot (e.g., delete the slot) or may be related to the data stored in the slot (e.g., insert data into the slot or delete the data in the slot).
- a subscribed event occurs whenever the specified operation is actually performed on the particular slot.
- the RMF web client waits to receive the subscribed event.
- the web client receives an event at act 1150.
- the event may be sent encoded which is parsed at act 1155.
- Each event may be sent with a unique identification associated with a particular session of a particular web client. Such identification is recognized at act 1160.
- the event is dispatched, at act 1165, to the web client according to the identification.
- Fig. 12 is an exemplary flowchart of a process, in which an RMF server interacts with an RMF web client and event producers to facilitate a web-enabled 2-way messaging communication.
- an event producer first registers itself, at act 1205, with the RMF server 160. The registered information may be stored in the producer registry 255 (Fig. 4).
- the RMF server receives, at act 1210, a request to establish a remote messaging session from a web client (via a corresponding RMF web client). The request may indicate an event producer with which the requested session is established.
- the RMF server 160 sets up, at act 1250, a listening connection.
- the listening connection may be established automatically when the event is successfully subscribed. It may also be established based on an explicit request from the web client to establish a listening connection. The latter is possible because the web client may temporarily disconnect the listening connection and later revive the connection.
- the RMF server determines, at act 1270, whether there is any filtering operation to be performed on the event. If there is, a filter agent is invoked at act 1275. Such a filter agent may correspond to a based filter agent 250, located in the RMF server 160, or a filter agent 290 located in the underlying event producer (Fig. 4). The event is then added, at act 1280, to the channel dedicated to the web client.
- the channel manager 235 once the notification is added to the channel dedicated to the web client, forwards the notification, at act 1285, to the web server 155 so that the notification is to be encoded, at act 1290, using a web protocol and then sent, at act 1295, to the web client.
- Fig. 13 is an exemplary flowchart of a process, in which an event producer conducts a 2-way remote messaging communication with a web client by interfacing with the RMF server.
- the event producer first sets up, at act 1310, part of the access control profile relevant to the event producer. It may then registers itself with the RMF server 160 at act 1320.
- the event producer may also specify a session agent, at act 1330, that performs authentication on web clients for the event producer.
- the request may be processed first by the RMF server 160 and authentication may be performed prior to starting a requested session.
- the RMF server 160 may invoke the session agent in the event producer to execute the authentication.
- the event producer receives the authentication request from the RMF server at act 1340 and performs the authentication on the requesting web client at act 1350.
- the event producer manipulates the message board, at act 1360, in the RMF server 160 through the RMF server API 265 (Fig. 2). If such manipulation fits the specification of a subscribed event, an event is generated in the RMF server 160 and may be filtered using the filter agent in the event producer. In this case, the RMF server 160 sends a request to the event producer for filtering an event. The event producer receives the filtering request at act 1370 and filters the event at act 1380.
- RemoteEventListener public void handleEvent (ServerEvent event); ⁇
- Interface ResponseListener f public void handleResponse (Dataltem result); ⁇
- class SimpleSlot public class SimpleSlot extends Slot ⁇ public SimpleSlot (String name) public SimpleSlot (String name, String accessCode) public Dataltem get() public void put (Dataltem data) public boolean isEmptyO public void clea () ⁇
- class ListSlot public class ListSlot extends Slot ⁇ public ListSlot (String name) public Dataltem get(mt index) public void put (Dataltem data) public void insert ( t index, Dataltem data) public void replace (mt index, Dataltem data) public void remove (mt index) public boolean contains (Object o) public void clear ( ) public boolean isEmptyO public int s ze() public Listlterator iterate (mt index)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP02739889A EP1402702B1 (en) | 2001-06-20 | 2002-06-13 | Web-enabled two-way remote messaging facility |
DE60231808T DE60231808D1 (en) | 2001-06-20 | 2002-06-13 | WEB-BASED TWO-WAY MACHINE TOOL |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/884,122 | 2001-06-20 | ||
US09/884,122 US20020198943A1 (en) | 2001-06-20 | 2001-06-20 | Web-enabled two-way remote messaging facility |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003001767A1 true WO2003001767A1 (en) | 2003-01-03 |
Family
ID=25383998
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2002/018959 WO2003001767A1 (en) | 2001-06-20 | 2002-06-13 | Web-enabled two-way remote messaging facility |
Country Status (7)
Country | Link |
---|---|
US (1) | US20020198943A1 (en) |
EP (1) | EP1402702B1 (en) |
CN (1) | CN100527732C (en) |
AT (1) | ATE427614T1 (en) |
DE (1) | DE60231808D1 (en) |
TW (1) | TWI229529B (en) |
WO (1) | WO2003001767A1 (en) |
Families Citing this family (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8037153B2 (en) * | 2001-12-21 | 2011-10-11 | International Business Machines Corporation | Dynamic partitioning of messaging system topics |
JP3744419B2 (en) * | 2001-12-27 | 2006-02-08 | 株式会社日立製作所 | Network device, network connection management device, and network device expansion method |
US7386615B1 (en) * | 2002-05-10 | 2008-06-10 | Oracle International Corporation | Method and system for reliably de-allocating resources in a networked computing environment |
US7073182B1 (en) * | 2002-06-21 | 2006-07-04 | Osburn Iii Douglas C | OPCMessenger |
US7802263B2 (en) | 2002-12-17 | 2010-09-21 | Stragent, Llc | System, method and computer program product for sharing information in a distributed framework |
CA2415043A1 (en) * | 2002-12-23 | 2004-06-23 | Ibm Canada Limited - Ibm Canada Limitee | A communication multiplexor for use with a database system implemented on a data processing system |
JP4305004B2 (en) * | 2003-02-28 | 2009-07-29 | ソニー株式会社 | Information processing apparatus, content information processing method, and computer program |
US7392316B2 (en) * | 2003-06-30 | 2008-06-24 | Microsoft Corporation | Client to server streaming of multimedia content using HTTP |
US7565534B2 (en) * | 2004-04-01 | 2009-07-21 | Microsoft Corporation | Network side channel for a message board |
US7487214B2 (en) * | 2004-11-10 | 2009-02-03 | Microsoft Corporation | Integrated electronic mail and instant messaging application |
US20070067780A1 (en) * | 2005-08-24 | 2007-03-22 | Samsung Electronics Co., Ltd. | Method and system for asynchronous eventing over the internet |
AU2007226892A1 (en) * | 2006-03-20 | 2007-09-27 | Google Inc. | Synchronous message management system |
KR101366803B1 (en) * | 2007-04-16 | 2014-02-24 | 삼성전자주식회사 | Communication method and apparatus using hyper text transfer protocol |
JP2009104254A (en) * | 2007-10-19 | 2009-05-14 | Sony Corp | Information delivery device, information delivery method and information delivery system |
US9015570B2 (en) * | 2007-12-21 | 2015-04-21 | Brighttalk Ltd. | System and method for providing a web event channel player |
US9032441B2 (en) * | 2007-12-21 | 2015-05-12 | BrightTALK Limited | System and method for self management of a live web event |
US9584564B2 (en) * | 2007-12-21 | 2017-02-28 | Brighttalk Ltd. | Systems and methods for integrating live audio communication in a live web event |
US20090216639A1 (en) * | 2008-02-25 | 2009-08-27 | Mark Joseph Kapczynski | Advertising selection and display based on electronic profile information |
US8243913B2 (en) | 2008-08-29 | 2012-08-14 | 8×8, Inc. | Limiting contact in a networked contact center environment |
US8972885B2 (en) | 2008-08-29 | 2015-03-03 | 8X8, Inc. | Networked contact center user interface |
US8515833B2 (en) * | 2008-08-29 | 2013-08-20 | 8X8, Inc. | Methods and systems for multilayer provisioning of networked contact centers |
US8275116B2 (en) * | 2008-08-29 | 2012-09-25 | 8X8, Inc. | Networked contact center |
US8204206B2 (en) * | 2008-08-29 | 2012-06-19 | 8X8, Inc. | Systems and methods for selection of a communication path |
US8977673B2 (en) | 2008-08-29 | 2015-03-10 | Red Hat, Inc. | Information on availability of services provided by publish-subscribe service |
US10033869B2 (en) * | 2008-08-29 | 2018-07-24 | 8X8, Inc. | Methods and systems for information streaming to user interface |
US9077750B2 (en) * | 2009-02-27 | 2015-07-07 | Red Hat, Inc. | Using forums as a message transport in an enterprise service bus |
US9215079B2 (en) * | 2010-04-18 | 2015-12-15 | Tropo, Inc. | Servlet API and method for XMPP protocol |
US8468545B2 (en) | 2010-08-18 | 2013-06-18 | 8X8, Inc. | Interaction management |
US9420030B2 (en) * | 2010-12-15 | 2016-08-16 | Brighttalk Ltd. | System and method for distributing web events via distribution channels |
US20130036058A1 (en) * | 2011-08-03 | 2013-02-07 | American Express Travel Related Services Company, Inc. | Systems and methods for securely processing transactions |
CA2851249C (en) * | 2011-10-05 | 2020-11-24 | Hartigen Solutions, Llc | Integrated software development and deployment architecture and high availability client-server systems generated using the architecture |
US11669584B2 (en) * | 2013-02-10 | 2023-06-06 | Wix.Com Ltd. | System and method for third party application activity data collection |
FR3004047A1 (en) * | 2013-03-29 | 2014-10-03 | France Telecom | TECHNIQUE OF COOPERATION BETWEEN A PLURALITY OF CLIENT ENTITIES |
US10148710B2 (en) | 2013-11-27 | 2018-12-04 | At&T Intellectual Property I, L.P. | Method, computer-readable storage device and apparatus for establishing persistent messaging sessions |
BR112016012695A8 (en) * | 2013-12-04 | 2020-05-12 | Wix Com Ltd | system and method for collecting activity data from third party applications |
CN105991579B (en) * | 2015-02-12 | 2019-05-28 | 华为技术有限公司 | Method for sending information, related network device and system |
CN108881456A (en) * | 2018-06-29 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of data interaction system, server-side and its data interactive method and system |
CN116881984B (en) * | 2023-09-08 | 2024-02-23 | 云筑信息科技(成都)有限公司 | Data monitoring method |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999048011A1 (en) * | 1998-03-20 | 1999-09-23 | Advanced Web Solutions, Inc. | Communication board system and method for use in computer networks |
US6020884A (en) * | 1996-11-08 | 2000-02-01 | America Online, Inc. | System integrating an on-line service community with a foreign service |
WO2001013259A1 (en) * | 1999-08-13 | 2001-02-22 | Iradius. Com, Inc. | Personal web platform service and system |
EP1083686A2 (en) * | 1999-09-10 | 2001-03-14 | Psuedo Programs, Inc. | System for providing interactive entertainment services to an audience using a communications network |
EP1107541A2 (en) * | 1999-12-07 | 2001-06-13 | Kizna.com Inc. | Client server system and data transmission method in a client server system |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5974446A (en) * | 1996-10-24 | 1999-10-26 | Academy Of Applied Science | Internet based distance learning system for communicating between server and clients wherein clients communicate with each other or with teacher using different communication techniques via common user interface |
US6038542A (en) * | 1998-04-28 | 2000-03-14 | Micron Electronics, Inc. | System for notifying an individual of a previously scheduled event |
US6351761B1 (en) * | 1998-12-18 | 2002-02-26 | At&T Corporation | Information stream management push-pull based server for gathering and distributing articles and messages specified by the user |
US6925513B1 (en) * | 1999-05-04 | 2005-08-02 | Apple Computer, Inc. | USB device notification |
US6571234B1 (en) * | 1999-05-11 | 2003-05-27 | Prophet Financial Systems, Inc. | System and method for managing online message board |
JP3542930B2 (en) * | 1999-07-30 | 2004-07-14 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Display information determination method and apparatus, storage medium storing software product for display information determination |
US6549776B1 (en) * | 1999-07-30 | 2003-04-15 | Telefonaktiebolaget Lm Ericsson (Publ) | System, method, and apparatus for pushing data in a direct digital call environment |
US6442565B1 (en) * | 1999-08-13 | 2002-08-27 | Hiddenmind Technology, Inc. | System and method for transmitting data content in a computer network |
US20020051017A1 (en) * | 2000-07-13 | 2002-05-02 | Clayton Wishoff | Notification device for a graphical user environment |
-
2001
- 2001-06-20 US US09/884,122 patent/US20020198943A1/en not_active Abandoned
-
2002
- 2002-06-13 AT AT02739889T patent/ATE427614T1/en not_active IP Right Cessation
- 2002-06-13 EP EP02739889A patent/EP1402702B1/en not_active Expired - Lifetime
- 2002-06-13 WO PCT/US2002/018959 patent/WO2003001767A1/en not_active Application Discontinuation
- 2002-06-13 TW TW091112861A patent/TWI229529B/en not_active IP Right Cessation
- 2002-06-13 DE DE60231808T patent/DE60231808D1/en not_active Expired - Lifetime
- 2002-06-13 CN CNB028160436A patent/CN100527732C/en not_active Expired - Fee Related
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6020884A (en) * | 1996-11-08 | 2000-02-01 | America Online, Inc. | System integrating an on-line service community with a foreign service |
WO1999048011A1 (en) * | 1998-03-20 | 1999-09-23 | Advanced Web Solutions, Inc. | Communication board system and method for use in computer networks |
WO2001013259A1 (en) * | 1999-08-13 | 2001-02-22 | Iradius. Com, Inc. | Personal web platform service and system |
EP1083686A2 (en) * | 1999-09-10 | 2001-03-14 | Psuedo Programs, Inc. | System for providing interactive entertainment services to an audience using a communications network |
EP1107541A2 (en) * | 1999-12-07 | 2001-06-13 | Kizna.com Inc. | Client server system and data transmission method in a client server system |
Non-Patent Citations (1)
Title |
---|
JONES G ET AL: "Web-based messaging management using Java servlets", INTEGRATED NETWORK MANAGEMENT. DISTRIBUTED MANAGEMENT FOR THE NETWORKED MILLENIUM. PROCEEDINGS OF THE IFIP/IEEE INTERNATIONAL SYMPOSIUM ON INTEGRATED NETWORK MANAGEMENT. PROCEEDINGS OF IM. IFIP/IEE INTERNATIONAL SYMPOSIUM ON INTEGRATED NETWORK MANAGE, 1999, pages 19 - 33, XP002166299 * |
Also Published As
Publication number | Publication date |
---|---|
EP1402702B1 (en) | 2009-04-01 |
CN100527732C (en) | 2009-08-12 |
EP1402702A1 (en) | 2004-03-31 |
US20020198943A1 (en) | 2002-12-26 |
TWI229529B (en) | 2005-03-11 |
CN1543738A (en) | 2004-11-03 |
DE60231808D1 (en) | 2009-05-14 |
ATE427614T1 (en) | 2009-04-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1402702B1 (en) | Web-enabled two-way remote messaging facility | |
JP4444518B2 (en) | A distributed system that establishes intelligent sessions between anonymous users over various networks | |
US7359978B2 (en) | Providing secure access through network firewalls | |
US7260623B2 (en) | Remote services system communication module | |
US6415318B1 (en) | Inter-enterprise messaging system using bridgehead servers | |
US8386577B2 (en) | Selection of communication protocol for message transfer based on quality of service requirements | |
JP4381655B2 (en) | Storage system, storage device, and information sharing method using the storage device | |
US20070005711A1 (en) | System and method for building instant messaging applications | |
EP1307822A2 (en) | A method, system and apparatus for establishing, monitoring, and managing connectivity for communication among heterogeneous systems | |
WO2008074748A2 (en) | Highly scalable real-time collaboration applications using http | |
US20030220977A1 (en) | Temporary aliasing for resource list | |
JP2013524632A (en) | Management of network communication between network nodes and stream transport protocol | |
JP2007524929A (en) | Enterprise collaboration system and method | |
US20090290503A1 (en) | Controlling Access to a Destination in a Data Processing Network | |
US7610386B1 (en) | Stateful messaging gateway | |
US20050270973A1 (en) | Cluster architecture communications | |
EP1333643A2 (en) | Remote services system data delivery mechanism | |
US8060568B2 (en) | Real time messaging framework hub to intercept and retransmit messages for a messaging facility | |
KR20040063646A (en) | Method for processing event of softswitch | |
US20030149771A1 (en) | Remote services system back-channel multicasting | |
US6594764B1 (en) | Apparatus, methods, and computer program products for network management operations relating to network management protocol adapter security software (mpass) for messaging with user name access identification | |
US20100070471A1 (en) | Transactional application events | |
Murata et al. | On shouting “fire!”: Regulating decoupled communication in distributed systems | |
Stiller et al. | Project Da CaPo++, volume I: Architectural and detailed design | |
DE60030176T2 (en) | Communication system to support interdependent messages |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2002739889 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20028160436 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2002739889 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |