WO2003094041A1 - System and method for storing large messages - Google Patents

System and method for storing large messages Download PDF

Info

Publication number
WO2003094041A1
WO2003094041A1 PCT/US2003/013586 US0313586W WO03094041A1 WO 2003094041 A1 WO2003094041 A1 WO 2003094041A1 US 0313586 W US0313586 W US 0313586W WO 03094041 A1 WO03094041 A1 WO 03094041A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
payload
integration component
store
integration
Prior art date
Application number
PCT/US2003/013586
Other languages
French (fr)
Inventor
David Wiser
Sanjay Dalal
Pascal Hoebanx
Original Assignee
Bea Systems, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bea Systems, Inc. filed Critical Bea Systems, Inc.
Priority to AU2003237146A priority Critical patent/AU2003237146A1/en
Publication of WO2003094041A1 publication Critical patent/WO2003094041A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
    • 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/06—Message adaptation to terminal or network requirements
    • H04L51/063—Content adaptation, e.g. replacement of unsuitable content
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99942—Manipulating data structure, e.g. compression, compaction, compilation

Definitions

  • the present invention relates to the storage of large messages in a computer system or on a computer network.
  • An integration component can receive an incoming message, such as from a Web server.
  • the integration component can separate the message into an "envelope" portion, which can contain information such as headers, protocols, and addresses, and a "payload” portion, which can contain items such as file attachments.
  • the integration component can write the envelope portion to local memory, and can write the payload portion to at least one persistent store.
  • a pointer can be placed in the envelope to identify the location of the payload in the persistent store.
  • Applications can then use the envelope to locate the payload in a persistent store.
  • An integration component can also process a message incrementally.
  • the integration component can process portions of the message until the payload portion is reached.
  • the integration component can then stop processing the message, but can continue to read the message in increments and write those increments to a persistent store.
  • Parsers such as MIME parsers and XML parsers can be used by the integration component to process the message.
  • the integration component can process the message as a stream, or at least write the payload portion to the persistent store as a stream.
  • Figure 1 is a diagram of a system in accordance with one embodiment of the present invention.
  • Figure 2 is a diagram of a message that can be processed using the system of Figure 1.
  • "large" messages such as large business messages in XML format, an be processed in a Web server or integration application.
  • These business messages can be Java Message Service (JMS) messages, for example, which can utilize distributed destinations in a cluster.
  • JMS Java Message Service
  • a large business message can be any message that may have an attachment or a large amount of text, for example, which can have an overall message size of at or above 1 MB, at or above 10MB, at or above 50 MB, or even at or above 100MB.
  • company A can send a message to company B that has a file size of 100 MB.
  • the integration system receiving that message will have to process and resend the entire message.
  • Local memory can be any appropriate storage medium, such as may be located on the Web server itself, in a cluster containing the Web server, or on a network node accessible to the Web server. If several large messages are received by the Web server 102, the server may eventually run out of memory.
  • portions of the body of each message can be stored in persistent storage 108 instead of being completely stored in local memory 106.
  • persistent storage There are at least two types of persistent storage, including file-based persistence stores and data-based persistence stores.
  • company B 110 can be working with an integration application.
  • the message can arrive on a socket on the network. Portions of the message can be stored somewhat directly to the persistent message store 108 instead of being read entirely into local memory 106.
  • One way to do this is to read the message in increments, or small portions, and write those small portions to storage. For example, the 100 MB message could have a 4 MB portion read into local memory 106, then have that 4 MB portion written to persistent storage 108. Then another 4 MB portion could be read into local memory and written to persistent storage. This process could continue until the entire body portion of the message is in persistent storage 108. Although portions of the entire message may be in memory at one point or another, there would only be up to 4 MB of the message in local memory at any given time.
  • the user can configure the persistent store 108 so that the message is sent to a file or to a database, for example.
  • the portion size can be any size appropriate for the size of the message or the capacity of the system, such as portions of 1 MB, 5 MB, or 10 MB.
  • the portion size can also be a percentage of the overall file size, such as 1 %, 5%, 10%, or 25%, for example.
  • the message can use a storage method referred to herein as "envelope plus payload.”
  • the message can be processed in the server to separate the contents to be placed in the "envelope” from contents to be placed in the "payload.” This is shown. forexample, in the diagram of Figure 2.
  • Headers 202, 204 of a message 200 can be extracted by an integration server, as the headers may be all the server requires to process the message 200.
  • a header can identify the protocol under which the message is sent, such as an XOCP protocol. The protocol can be used to help identify the headers 202, 204 and the body 206 of the message.
  • the headers can be placed in the envelope 214, which can be stored in local memory.
  • the body 206 of the message 200 which can contain several attachments 208, 210, 212, for example, can be placed into the payload 218.
  • the payload can be stored in persistent storage on the server, in the cluster, or on the network.
  • the envelope 214 can contain a pointer 216 to the location of the payload 218.
  • the payload can be designed to contain multiple parts as well. While processing a message in the server, however, only the envelope may be needed.
  • the payload can belong to the user of a B2B server, for example, or an application riding on top of an integration server.
  • the payload can be stored to persistent storage, so that the full payload is never stored in memory.
  • a server or any application can simply deal with the envelope, which can contain pointers to the payload.
  • the application can view information contained in the envelope, which can include identification information for the payload parts.
  • An application can use any pointers in an envelope to extract portions of the body of the message stored in the payload.
  • a message envelope can contain a pointer to the body of the message, whether there is a single message body or a number of portions, or can contain a pointer for each portion of the body in persistent storage.
  • the number of portions can include a number of attachments, for example. It is not necessary for the integration system to process the attachments to a message, so the system can simply write the attachments to storage, either all together in one block of memory or individually.
  • the pointer can point to the location at which a portion of the message body begins in memory, or can point to the boundaries of a given body portion in memory, for example.
  • An envelope can contain other useful information about a message, such as the address of the sender and/or the address of the recipient. Each of these addresses can each be a URL, for example.
  • the envelope can also contain the protocol of the message and possibly the protocol of any body portion, if applicable.
  • the envelope can contain message text.
  • the envelope can also contain information about each attachment in the body, such as title, file type, and historical information.
  • At least two levels of parsing can be used to process a message.
  • a low- level parsing mechanism can be used to decode transfer protocols such as MIME or UUENCODE.
  • the low-level parser can receive the byte stream and identify the parts of the message, such as a text portion and a binary attachment.
  • a second level of parsing such as XML parsing, can be used to read headers and body portions, which can be in XML or another appropriate messaging or mark-up language.
  • a message can arrive from the Internet, for example, and can pass through the Web server into an integration transport layer.
  • First, the message can pass through a MIME parser.
  • Second, the message can be decoded using a second processing layer to determine the appropriate business protocol.
  • the envelope can be created in this transport layer.
  • the decoding process which can use the XML parser, the envelope can be filled with headers and other appropriate information.
  • a pointer can be placed in the envelope and the MIME parser can stop parsing the message.
  • the MIME parser can know to stop parsing when it hits attachments, for example.
  • the remainder of the message which can include at least a portion of the body and any attachments, can then be written directly to persistent storage, either in small data "dumps" or on a data stream.
  • an application can determine where the message portions reside using pointers in the message envelope.
  • the envelope can be thought of as an "abstract" of the message.
  • a user or application gets this abstract, that user or application can extract any portion of the message that is needed. For instance, if there are three attachments, the user or application can choose to extract one or two of the attachments from the persistent storage.
  • the envelope can be used, such as by an integration server or B2B server, to delete the associated portions in the persistent storage.

Abstract

A large message (200) can be stored by separating the message (200) into an envelope portion containing information such as headers (202, 204), protocols, and addresses, and a payload portion (218) containing items such as file attachments. The envelope portion (214) can be stored in local storage, while the payload (218) can be stored to a persistent store. The message (200) can be processed incrementally, such that the entire message (200) is never in system memory. Once the envelope portion (214) is processed, the payload portion (218) can be read in increments without being processed, and those increments written directly to the persistent store. Alternatively, the payload (218) can be streamed to the persistent store. A pointer (216) in the envelope (214) can then be used to locate and retrieve attachments (208, 210, 212) from persistent storage.

Description

System and Method for Storing Large Messages
CLAIM OF PRIORITY This application claims priority to U.S. Provisional Patent Application No. 60/376,773, filed May 1, 2002, entitled "System and Method for Storing Large Messages," which is hereby incorporated herein by reference.
COPYRIGHT NOTICE A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document of the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
CROSS-REFERENCED CASES
The following applications are cross-referenced and incorporated herein by reference:
U.S. Patent Application No. 10/404,552 filed April 1 , 2003, to Mike Blevins et al. and entitled, "COLLABORATIVE BUSINESS PLUG-IN FRAMEWORK"; U.S. Patent Application No. 10/404,684 filed April 1 , 2003, to Mike Blevins et al. and entitled, "SYSTEMS AND METHODS FOR BUSINESS PROCESS PLUG-IN DEVELOPMENT"; and
U.S. Patent Application No. 10/404,666 filed April 1 , 2003, to David Wiser et al. and entitled "Single Servlets for B2B Message Routing."
FIELD OF THE INVENTION The present invention relates to the storage of large messages in a computer system or on a computer network.
BACKGROUND
Existing integration and messaging systems have problems handling large messages. Incoming messages are read into memory in their entirety, such that when a number of large messages are received a system can crash due to a lack of available memory. Some systems try to prevent these problems by limiting the size of messages that can be processed through a system, but this approach is undesirable to users needing to send messages that may occasionally exceed that limitation.
Another existing approach utilizes in-database persistence and in-memory caching on a hub. Persistence saves enough data for recovery purposes, and caching allows messages to be serialized to a Java Message Service (JMS). This allows JMS to enqueue faster, and allows a JMS dequeue to request the message from a cache without having to redo expensive operations like deserialization, decryption, and XML parsing. The problem still exists in that it is necessary to read an entire message into memory in order to process the message.
BRIEF SUMMARY Systems and methods in accordance with embodiments of the present invention can overcome deficiencies in existing messaging systems by changing the way in which messages are processed and stored. An integration component can receive an incoming message, such as from a Web server. The integration component can separate the message into an "envelope" portion, which can contain information such as headers, protocols, and addresses, and a "payload" portion, which can contain items such as file attachments. The integration component can write the envelope portion to local memory, and can write the payload portion to at least one persistent store. A pointer can be placed in the envelope to identify the location of the payload in the persistent store. Applications can then use the envelope to locate the payload in a persistent store.
An integration component can also process a message incrementally. The integration component can process portions of the message until the payload portion is reached. The integration component can then stop processing the message, but can continue to read the message in increments and write those increments to a persistent store. Parsers such as MIME parsers and XML parsers can be used by the integration component to process the message. Alternatively, the integration component can process the message as a stream, or at least write the payload portion to the persistent store as a stream.
Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a diagram of a system in accordance with one embodiment of the present invention. Figure 2 is a diagram of a message that can be processed using the system of Figure 1.
DETAILED DESCRIPTION In systems and methods in accordance with embodiments of the present invention, "large" messages, such as large business messages in XML format, an be processed in a Web server or integration application. These business messages can be Java Message Service (JMS) messages, for example, which can utilize distributed destinations in a cluster. A large business message can be any message that may have an attachment or a large amount of text, for example, which can have an overall message size of at or above 1 MB, at or above 10MB, at or above 50 MB, or even at or above 100MB. For example, company A can send a message to company B that has a file size of 100 MB. The integration system receiving that message will have to process and resend the entire message. In existing systems, it is necessary to read the entire message into memory before writing the message to disk. The read and write are each done in one complete step. Present systems also have to parse the entire message.
As shown in Figure 1, when a message from a company A 100 is first received to an integration component 104 from a Web server 102, the message can be read into local memory 106. Local memory can be any appropriate storage medium, such as may be located on the Web server itself, in a cluster containing the Web server, or on a network node accessible to the Web server. If several large messages are received by the Web server 102, the server may eventually run out of memory. In a system in accordance with one embodiment of the present invention, portions of the body of each message can be stored in persistent storage 108 instead of being completely stored in local memory 106. There are at least two types of persistent storage, including file-based persistence stores and data-based persistence stores. Continuing with the example, company B 110 can be working with an integration application. When the message arrives at the Web server 102 for company B 110, the message can arrive on a socket on the network. Portions of the message can be stored somewhat directly to the persistent message store 108 instead of being read entirely into local memory 106. One way to do this is to read the message in increments, or small portions, and write those small portions to storage. For example, the 100 MB message could have a 4 MB portion read into local memory 106, then have that 4 MB portion written to persistent storage 108. Then another 4 MB portion could be read into local memory and written to persistent storage. This process could continue until the entire body portion of the message is in persistent storage 108. Although portions of the entire message may be in memory at one point or another, there would only be up to 4 MB of the message in local memory at any given time. The user can configure the persistent store 108 so that the message is sent to a file or to a database, for example. The portion size can be any size appropriate for the size of the message or the capacity of the system, such as portions of 1 MB, 5 MB, or 10 MB. The portion size can also be a percentage of the overall file size, such as 1 %, 5%, 10%, or 25%, for example.
When a message is processed using an integration application or integration server, for example, the message can use a storage method referred to herein as "envelope plus payload." The message can be processed in the server to separate the contents to be placed in the "envelope" from contents to be placed in the "payload." This is shown. forexample, in the diagram of Figure 2. Headers 202, 204 of a message 200 can be extracted by an integration server, as the headers may be all the server requires to process the message 200. A header can identify the protocol under which the message is sent, such as an XOCP protocol. The protocol can be used to help identify the headers 202, 204 and the body 206 of the message. It can be important in certain systems to identify the message protocol, as protocols such as RosettaNet and ebXML have different packaging semantics than a protocol such as XOCP. The headers can be placed in the envelope 214, which can be stored in local memory. The body 206 of the message 200, which can contain several attachments 208, 210, 212, for example, can be placed into the payload 218. The payload can be stored in persistent storage on the server, in the cluster, or on the network. The envelope 214 can contain a pointer 216 to the location of the payload 218.
Since a message can contain a body with multiple parts, the payload can be designed to contain multiple parts as well. While processing a message in the server, however, only the envelope may be needed. The payload can belong to the user of a B2B server, for example, or an application riding on top of an integration server. The payload can be stored to persistent storage, so that the full payload is never stored in memory. A server or any application can simply deal with the envelope, which can contain pointers to the payload. When an application wants to access any portion of the message, the application can view information contained in the envelope, which can include identification information for the payload parts. An application can use any pointers in an envelope to extract portions of the body of the message stored in the payload. As the application can retrieve the data from this persistence store, it is not necessary to accumulate everything in local memory on the integration server. A message envelope can contain a pointer to the body of the message, whether there is a single message body or a number of portions, or can contain a pointer for each portion of the body in persistent storage. The number of portions can include a number of attachments, for example. It is not necessary for the integration system to process the attachments to a message, so the system can simply write the attachments to storage, either all together in one block of memory or individually. The pointer can point to the location at which a portion of the message body begins in memory, or can point to the boundaries of a given body portion in memory, for example. An envelope can contain other useful information about a message, such as the address of the sender and/or the address of the recipient. Each of these addresses can each be a URL, for example. The envelope can also contain the protocol of the message and possibly the protocol of any body portion, if applicable. The envelope can contain message text. The envelope can also contain information about each attachment in the body, such as title, file type, and historical information.
At least two levels of parsing can be used to process a message. A low- level parsing mechanism can be used to decode transfer protocols such as MIME or UUENCODE. The low-level parser can receive the byte stream and identify the parts of the message, such as a text portion and a binary attachment. A second level of parsing, such as XML parsing, can be used to read headers and body portions, which can be in XML or another appropriate messaging or mark-up language.
A message can arrive from the Internet, for example, and can pass through the Web server into an integration transport layer. First, the message can pass through a MIME parser. Second, the message can be decoded using a second processing layer to determine the appropriate business protocol. The envelope can be created in this transport layer. In the decoding process, which can use the XML parser, the envelope can be filled with headers and other appropriate information. After the headers, a pointer can be placed in the envelope and the MIME parser can stop parsing the message. The MIME parser can know to stop parsing when it hits attachments, for example.
The remainder of the message, which can include at least a portion of the body and any attachments, can then be written directly to persistent storage, either in small data "dumps" or on a data stream. Once the entire message is processed, such that the envelope and payload are created, an application can determine where the message portions reside using pointers in the message envelope. The envelope can be thought of as an "abstract" of the message. Once a user or application gets this abstract, that user or application can extract any portion of the message that is needed. For instance, if there are three attachments, the user or application can choose to extract one or two of the attachments from the persistent storage. When the user deletes the message, the envelope can be used, such as by an integration server or B2B server, to delete the associated portions in the persistent storage.
The foregoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to one of ordinary skill in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence.

Claims

CLAIMS What is claimed is:
1. A system for storing a message, comprising: a memory component adapted to temporarily store information for the message; a persistent store adapted to persistently store information for the message; and an integration component for receiving the message, the integration component adapted to separate the message into an envelope portion and a payload portion, the integration component adapted to store the envelope portion in the memory component and adapted to store the payload portion in the persistent store.
2. A system according to claim 1 , wherein: the integration component is adapted to separate the message into an envelope portion containing information selected from the group consisting of headers, protocols, addresses, and message text.
3. A system according to claim 1 , wherein: the integration component is adapted to separate the message into a payload portion containing message attachments.
4. A system according to claim 1 , further comprising: a Web server adapted to receive the message and direct the message to the integration component
5. A system according to claim 1 , wherein: the persistent store is selected from group consisting of file-based persistent stores and data-based persistent stores.
6. A system according to claim 1 , wherein: the integration component is further adapted to process message in increments of the overall message size.
7. A system according to claim 5, wherein: the integration component is further adapted to write the payload to the persistent store in increments.
8. A system according to claim 1 , wherein: the integration component is further adapted to process message in increments each having a size selected from the group consisting of 1 MB, 5 MB, or 10 MB.
9. A system according to claim 1 , wherein: the integration component is further adapted to process message in increments each having a size selected from the group consisting of 1%, 5%, 10%, and 25% of the overall file size.
10. A system according to claim 1 , wherein: the integration component is selected from the group consisting of integration applications, integration servers, integration transport layers, and integration plug-ins.
11. A system according to claim 1 , wherein: the integration component is further adapted to place a pointer in the envelope, the pointer indicating the location of the payload portion in the persistent store.
12. A system according to claim 1 , wherein: the integration component is adapted to store the payload portion in the persistent store, wherein the payload is stored in multiple locations in the persistent store.
13. A system according to claim 1 , wherein: the integration component is adapted to store the payload portion in the persistent store and any other persistent store, wherein the payload portion can be stored to more than one persistent store.
14. A system according to claim 1 , further comprising: a protocol parser adapted to identify portions of the message to the integration component.
15. A system according to claim 14, wherein: the protocol parser is further adapted to stop parsing the protocol parser when reaches payload portion of the message.
16. A system according to claim 1 , further comprising: an XML parser for reading header and body portions of the message.
17. A system according to claim 1 , wherein: the integration component is further adapted to store the payload portion to the persistent store in a stream without processing the payload portion.
18. A system according to claim 1 , wherein: the integration component is adapted to receive messages in XML.
19. A system according to claim 1 , wherein: the integration component is adapted to receive messages having a file size selected from the group consisting of at or above 1 MB, at or above 10 MB, at or above 50 MB, and at or above 100 MB.
20. A method for storing a message, comprising: receiving the message to an integration component; separating the message into an envelope portion and a payload portion; storing the envelope portion to local storage; and storing the payload to at least one persistent store.
21. A method according to claim 20, further comprising: parsing the message with a protocol parser to identify portions of the message to the integration component.
22. A method according to claim 20, further comprising: parsing the message with an XML parser to read header and body portions of the message.
23. A method according to claim 20, further comprising: processing the message in increments.
24. A method according to claim 20, further comprising: processing the message as a stream.
25. A method according to claim 20, further comprising: placing a pointer in the envelope portion to identify the location of the payload portion in the persistent store.
26. A computer-readable medium, comprising: means for receiving the message to an integration component; means for separating the message into an envelope portion and a payload portion; means for storing the envelope portion to local storage; and means for storing the payload to at least one persistent store.
27. A computer program product for execution by a server computer for storing a message, comprising: computer code for receiving the message to an integration component; computer code for separating the message into an envelope portion and a payload portion; computer code for storing the envelope portion to local storage; and computer code for storing the payload to at least one persistent store.
28. A system for storing a message, comprising: means for receiving the message to an integration component; means for separating the message into an envelope portion and a payload portion; means for storing the envelope portion to local storage; and means for storing the payload to at least one persistent store.
9. A computer system comprising: a processor; object code executed by said processor, said object code configured to: receive the message to an integration component; separate the message into an envelope portion and a payload portion; store the envelope portion to local storage; and store the payload to at least one persistent store.
PCT/US2003/013586 2002-05-01 2003-04-30 System and method for storing large messages WO2003094041A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003237146A AU2003237146A1 (en) 2002-05-01 2003-04-30 System and method for storing large messages

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US37677302P 2002-05-01 2002-05-01
US60/376,773 2002-05-01
US10/404,865 2003-04-01
US10/404,865 US7257645B2 (en) 2002-05-01 2003-04-01 System and method for storing large messages

Publications (1)

Publication Number Publication Date
WO2003094041A1 true WO2003094041A1 (en) 2003-11-13

Family

ID=29406767

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/013586 WO2003094041A1 (en) 2002-05-01 2003-04-30 System and method for storing large messages

Country Status (3)

Country Link
US (2) US7257645B2 (en)
AU (1) AU2003237146A1 (en)
WO (1) WO2003094041A1 (en)

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7826457B2 (en) * 2004-05-11 2010-11-02 Broadcom Corp. Method and system for handling out-of-order segments in a wireless system via direct data placement
US8903760B2 (en) * 2004-11-12 2014-12-02 International Business Machines Corporation Method and system for information workflows
US7933928B2 (en) * 2005-12-22 2011-04-26 Oracle International Corporation Method and mechanism for loading XML documents into memory
US7933935B2 (en) * 2006-10-16 2011-04-26 Oracle International Corporation Efficient partitioning technique while managing large XML documents
US8051428B2 (en) * 2008-03-13 2011-11-01 Sap Ag Definition of an integrated notion of a message scenario for several messaging components
US8429196B2 (en) 2008-06-06 2013-04-23 Oracle International Corporation Fast extraction of scalar values from binary encoded XML
SE533007C2 (en) 2008-10-24 2010-06-08 Ilt Productions Ab Distributed data storage
US9177264B2 (en) 2009-03-06 2015-11-03 Chiaramail, Corp. Managing message categories in a network
EP2387200B1 (en) 2010-04-23 2014-02-12 Compuverde AB Distributed data storage
US8566577B2 (en) * 2010-11-30 2013-10-22 Blackberry Limited Method and device for storing secured sent message data
US20120296990A1 (en) * 2011-05-16 2012-11-22 Uomini Robert G Shared content server for electronic messages
US8635292B2 (en) * 2011-05-16 2014-01-21 Robert Uomini Method for reduction of disk space usage of electronic messages in a network
US9626378B2 (en) 2011-09-02 2017-04-18 Compuverde Ab Method for handling requests in a storage system and a storage node for a storage system
US8645978B2 (en) 2011-09-02 2014-02-04 Compuverde Ab Method for data maintenance
US8769138B2 (en) 2011-09-02 2014-07-01 Compuverde Ab Method for data retrieval from a distributed data storage system
US8997124B2 (en) 2011-09-02 2015-03-31 Compuverde Ab Method for updating data in a distributed data storage system
US8650365B2 (en) 2011-09-02 2014-02-11 Compuverde Ab Method and device for maintaining data in a data storage system comprising a plurality of data storage nodes
US9021053B2 (en) 2011-09-02 2015-04-28 Compuverde Ab Method and device for writing data to a data storage system comprising a plurality of data storage nodes
US9338108B2 (en) 2012-07-23 2016-05-10 Xpedite Systems, Llc Inter-modal messaging communications
US9141340B2 (en) * 2013-05-31 2015-09-22 Oracle International Corporation Integration message resubmission tool
US10498648B1 (en) 2015-03-25 2019-12-03 Amazon Technologies, Inc. Processing packet data using an offload engine in a service provider environment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6345283B1 (en) * 1998-07-20 2002-02-05 New Technologies Armor, Inc. Method and apparatus for forensic analysis of information stored in computer-readable media
US6348970B1 (en) * 1998-04-29 2002-02-19 Qwest Communications Int'l., Inc. Apparatus and method for interfacing a computer network to a facsimile machine
US6360221B1 (en) * 1999-09-21 2002-03-19 Neostar, Inc. Method and apparatus for the production, delivery, and receipt of enhanced e-mail

Family Cites Families (197)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5187790A (en) 1989-06-29 1993-02-16 Digital Equipment Corporation Server impersonation of client processes in an object based computer operating system
US5555201A (en) 1990-04-06 1996-09-10 Lsi Logic Corporation Method and system for creating and validating low level description of electronic design from higher level, behavior-oriented description, including interactive system for hierarchical display of control and dataflow information
IL100987A (en) 1991-02-27 1995-10-31 Digital Equipment Corp Method and apparatus for compiling code
US5469562A (en) 1992-06-26 1995-11-21 Digital Equipment Corporation Durable atomic storage update manager
US5944794A (en) 1994-09-30 1999-08-31 Kabushiki Kaisha Toshiba User identification data management scheme for networking computer systems using wide area network
US5604860A (en) 1994-10-27 1997-02-18 Xerox Corporation Feature library and stored customized control interfaces
US5630131A (en) 1994-11-14 1997-05-13 Object Technology Licensing Corp. Method and apparatus for importing and exporting archive files for a graphical user interface
US5748975A (en) 1995-07-06 1998-05-05 Sun Microsystems, Inc. System and method for textual editing of structurally-represented computer programs with on-the-fly typographical display
US5835769A (en) 1995-09-19 1998-11-10 Sun Microsystems, Inc. Apparatti and computer program products for integrating editors with applications
US5966535A (en) 1995-12-07 1999-10-12 At&T Corporation Method and apparatus for generating program code for world wide web service applications
SE517033C2 (en) 1995-12-08 2002-04-02 Ericsson Telefon Ab L M System platform for communication systems
EP0888585A1 (en) 1996-03-19 1999-01-07 Massachusetts Institute Of Technology Computer system and computer implemented process for representing software system descriptions and for generating executable computer programs and computer system configurations from software system descriptions
DE19712946A1 (en) 1996-05-30 1997-12-04 Ibm Computerised method of automatically expanding specifications of process model in workflow process environment
US5862327A (en) 1996-06-10 1999-01-19 Tactica Corporation Activity based long-lived transaction system
US5867822A (en) 1996-06-26 1999-02-02 Sun Microsystems, Inc. Method and apparatus for management of electronic calendars throughout an enterprise and management of events in a distributed system
US6012083A (en) 1996-09-24 2000-01-04 Ricoh Company Ltd. Method and apparatus for document processing using agents to process transactions created based on document content
US5950010A (en) 1996-11-25 1999-09-07 J.D. Edwards World Source Co. System and method for customized application package building and installation
GB2320112B (en) 1996-12-07 2001-07-25 Ibm High-availability computer server system
US5961593A (en) 1997-01-22 1999-10-05 Lucent Technologies, Inc. System and method for providing anonymous personalized browsing by a proxy system in a network
US5933838A (en) 1997-03-10 1999-08-03 Microsoft Corporation Database computer system with application recovery and recovery log sequence numbers to optimize recovery
US6353923B1 (en) 1997-03-12 2002-03-05 Microsoft Corporation Active debugging environment for debugging mixed-language scripting code
WO1998040850A2 (en) 1997-03-13 1998-09-17 Whitney Mark M A system for, and method of, off-loading network transactions from a mainframe to an intelligent input/output device, including off-loading message queuing facilities
CA2201278C (en) 1997-03-27 2001-02-20 Ibm Canada Limited-Ibm Canada Limitee Hierarchical metadata store for an integrated development environment
US6230309B1 (en) 1997-04-25 2001-05-08 Sterling Software, Inc Method and system for assembling and utilizing components in component object systems
US6085030A (en) 1997-05-02 2000-07-04 Novell, Inc. Network component server
US6023578A (en) 1997-05-09 2000-02-08 International Business Macines Corporation Systems, methods and computer program products for generating an object oriented application for an object oriented environment
US5987376A (en) 1997-07-16 1999-11-16 Microsoft Corporation System and method for the distribution and synchronization of data and state information between clients in a distributed processing system
US6366663B1 (en) 1997-07-21 2002-04-02 Mci Communications Corporation System for achieving local number portability
US6222533B1 (en) 1997-08-25 2001-04-24 I2 Technologies, Inc. System and process having a universal adapter framework and providing a global user interface and global messaging bus
US6070184A (en) 1997-08-28 2000-05-30 International Business Machines Corporation Server-side asynchronous form management
CA2246130C (en) 1997-09-04 2003-01-14 Mitel Corporation Web based help desk
US6016495A (en) 1997-09-19 2000-01-18 International Business Machines Corporation Object-oriented framework mechanism for providing persistent storage
US6470386B1 (en) 1997-09-26 2002-10-22 Worldcom, Inc. Integrated proxy interface for web based telecommunications management tools
US6092102A (en) 1997-10-24 2000-07-18 University Of Pittsburgh Of The Commonwealth System Of Higher Education System and method for notifying users about information or events of an enterprise
US6334114B1 (en) 1997-10-31 2001-12-25 Oracle Corporation Method and apparatus for performing transactions in a stateless web environment which supports a declarative paradigm
US6067623A (en) 1997-11-21 2000-05-23 International Business Machines Corp. System and method for secure web server gateway access using credential transform
US6029000A (en) 1997-12-22 2000-02-22 Texas Instruments Incorporated Mobile communication system with cross compiler and cross linker
FI106831B (en) 1998-01-14 2001-04-12 Nokia Networks Oy Access control procedure for a mobile telephone system
US6594693B1 (en) 1998-02-10 2003-07-15 Nitin A. Borwankar Method and apparatus for a structured, synchronized conversation using electronic messages over a computer network
US6480206B2 (en) 1998-02-24 2002-11-12 Sun Microsystems, Inc. Method and apparatus for an extensible editor
US6311327B1 (en) 1998-03-02 2001-10-30 Applied Microsystems Corp. Method and apparatus for analyzing software in a language-independent manner
US6148336A (en) * 1998-03-13 2000-11-14 Deterministic Networks, Inc. Ordering of multiple plugin applications using extensible layered service provider with network traffic filtering
US6141686A (en) 1998-03-13 2000-10-31 Deterministic Networks, Inc. Client-side application-classifier gathering network-traffic statistics and application and user names using extensible-service provider plugin for policy-based network control
US6349408B1 (en) 1998-03-23 2002-02-19 Sun Microsystems, Inc. Techniques for implementing a framework for extensible applications
US6947943B2 (en) * 2001-10-26 2005-09-20 Zeosoft Technology Group, Inc. System for development, management and operation of distributed clients and servers
US6338064B1 (en) 1998-05-14 2002-01-08 International Business Machines Corporation Method for enabling a web server running a “closed” native operating system to impersonate a user of a web client to obtain a protected file
US6119149A (en) 1998-06-05 2000-09-12 I2 Technologies, Inc. System and process allowing collaboration within and between enterprises for optimal decision making
US6237135B1 (en) 1998-06-18 2001-05-22 Borland Software Corporation Development system with visual design tools for creating and maintaining Java Beans components
US6067548A (en) 1998-07-16 2000-05-23 E Guanxi, Inc. Dynamic organization model and management computing system and method therefor
US6343265B1 (en) 1998-07-28 2002-01-29 International Business Machines Corporation System and method for mapping a design model to a common repository with context preservation
WO2000014618A2 (en) 1998-08-24 2000-03-16 Fujitsu Limited Workflow system and method
US6963914B1 (en) 1998-09-01 2005-11-08 Lucent Technologies Inc. Method and apparatus for retrieving a network file using a logical reference
US6212546B1 (en) 1998-10-01 2001-04-03 Unisys Corporation Providing a modular gateway architecture which isolates attributes of the client and server systems into independent components
US6324681B1 (en) 1998-10-01 2001-11-27 Unisys Corporation Automated development system for developing applications that interface with both distributed component object model (DCOM) and enterprise server environments
US6189044B1 (en) 1998-10-14 2001-02-13 Hughes Electronics Corporation Dynamic routing method for packet switched satellite communications
US6336122B1 (en) 1998-10-15 2002-01-01 International Business Machines Corporation Object oriented class archive file maker and method
US6226675B1 (en) 1998-10-16 2001-05-01 Commerce One, Inc. Participant server which process documents for commerce in trading partner networks
US6393605B1 (en) 1998-11-18 2002-05-21 Siebel Systems, Inc. Apparatus and system for efficient delivery and deployment of an application
US6385724B1 (en) 1998-11-30 2002-05-07 Microsoft Corporation Automatic object caller chain with declarative impersonation and transitive trust
US6637020B1 (en) 1998-12-03 2003-10-21 International Business Machines Corporation Creating applications within data processing systems by combining program components dynamically
US6018730A (en) 1998-12-22 2000-01-25 Ac Properties B.V. System, method and article of manufacture for a simulation engine with a help website and processing engine
US6795967B1 (en) 1999-01-26 2004-09-21 Microsoft Corporation Changing user identities without closing applications
JP4146983B2 (en) 1999-02-26 2008-09-10 インターナショナル・ビジネス・マシーンズ・コーポレーション Process method and data processing system for calling method of server object
US6360358B1 (en) 1999-03-11 2002-03-19 Microsoft Corporation Maintenance of code knowledge for up-to-date access thereof
US6243737B1 (en) * 1999-04-09 2001-06-05 Translink Software, Inc. Method and apparatus for providing direct transaction access to information residing on a host system
AU4482000A (en) 1999-04-23 2000-11-10 Sony Electronics Inc. Method of and apparatus for implementing and sending an asynchronous control mechanism packet
US6789054B1 (en) 1999-04-25 2004-09-07 Mahmoud A. Makhlouf Geometric display tools and methods for the visual specification, design automation, and control of adaptive real systems
US6377939B1 (en) 1999-05-04 2002-04-23 Metratech Pipelined method and apparatus for processing communication metering data
US6463503B1 (en) 1999-05-12 2002-10-08 International Business Machines Corporation Method and system for increasing concurrency during staging and destaging in a log structured array
US6292932B1 (en) 1999-05-28 2001-09-18 Unisys Corp. System and method for converting from one modeling language to another
US7472349B1 (en) 1999-06-01 2008-12-30 Oracle International Corporation Dynamic services infrastructure for allowing programmatic access to internet and other resources
US6594700B1 (en) 1999-06-14 2003-07-15 International Business Machines Corporation System and method for implementing a universal service broker interchange mechanism
US6330569B1 (en) 1999-06-30 2001-12-11 Unisys Corp. Method for versioning a UML model in a repository in accordance with an updated XML representation of the UML model
US6408311B1 (en) 1999-06-30 2002-06-18 Unisys Corp. Method for identifying UML objects in a repository with objects in XML content
US6880126B1 (en) 1999-08-03 2005-04-12 International Business Machines Corporation Controlling presentation of a GUI, using view controllers created by an application mediator, by identifying a destination to access a target to retrieve data
US6282711B1 (en) 1999-08-10 2001-08-28 Hewlett-Packard Company Method for more efficiently installing software components from a remote server source
US7200563B1 (en) 1999-08-20 2007-04-03 Acl International Inc. Ontology-driven information system
US6549949B1 (en) 1999-08-31 2003-04-15 Accenture Llp Fixed format stream in a communication services patterns environment
US7051316B2 (en) 1999-10-05 2006-05-23 Borland Software Corporation Distributed computing component system with diagrammatic graphical representation of code with separate delineated display area by type
FR2800183B1 (en) * 1999-10-26 2002-02-22 Bull Sa SYSTEM AND METHOD FOR MANAGING THE PERSISTENCE OF EJB COMPONENTS IN A DIRECTORY ACCESSED BY LDAP
US6802000B1 (en) 1999-10-28 2004-10-05 Xerox Corporation System for authenticating access to online content referenced in hardcopy documents
US6748420B1 (en) 1999-11-23 2004-06-08 Cisco Technology, Inc. Methods and apparatus for providing shared access to an application
AU2062301A (en) 1999-12-06 2001-06-25 Bios Group Inc. A method and system for discovery of trades between parties
US6678518B2 (en) 1999-12-09 2004-01-13 Nokia Corporation Dynamic content filter in a gateway
CN1128531C (en) 1999-12-30 2003-11-19 国际商业机器公司 Plug-in type service transmission platform
US20020010781A1 (en) 1999-12-30 2002-01-24 Tuatini Jeffrey Taihana Shared service messaging models
US6609115B1 (en) 1999-12-30 2003-08-19 Ge Medical Systems Method and apparatus for limited online access to restricted documentation
US6584454B1 (en) 1999-12-31 2003-06-24 Ge Medical Technology Services, Inc. Method and apparatus for community management in remote system servicing
US6643652B2 (en) * 2000-01-14 2003-11-04 Saba Software, Inc. Method and apparatus for managing data exchange among systems in a network
WO2001052090A2 (en) * 2000-01-14 2001-07-19 Saba Software, Inc. Method and apparatus for a web content platform
AU2001229371A1 (en) 2000-01-14 2001-07-24 Saba Software, Inc. Information server
AU2001227857A1 (en) 2000-01-14 2001-07-24 Saba Software, Inc. Method and apparatus for a business applications management system platform
AU2001229660A1 (en) 2000-02-14 2001-08-27 Ubs Painewebber Inc. System for providing financial services
AU2001238380A1 (en) 2000-02-16 2001-08-27 Bea Systems Inc. Open market collaboration system for enterprise wide electronic commerce
JP2001243366A (en) * 2000-02-25 2001-09-07 Hitachi Ltd Server having trade job supporting function
AU2001245976A1 (en) 2000-03-29 2001-10-08 Nextset Software Inc. System and method of providing an asynchronous interface between a client system and an enterprise javabeans-enabled server
US20040148336A1 (en) * 2000-03-30 2004-07-29 Hubbard Edward A Massively distributed processing system architecture, scheduling, unique device identification and associated methods
US6925482B2 (en) 2000-04-14 2005-08-02 Slam Dunk Networks, Inc. Archival database system for handling information and information transfers in a computer network
US6516322B1 (en) 2000-04-28 2003-02-04 Microsoft Corporation XML-based representation of mobile process calculi
US6918084B1 (en) 2000-05-09 2005-07-12 Sun Microsystems, Inc. Spawning new repository spaces using information provided in advertisement schema messages
US6850979B1 (en) 2000-05-09 2005-02-01 Sun Microsystems, Inc. Message gates in a distributed computing environment
US6971096B1 (en) 2000-05-19 2005-11-29 Sun Microsystems, Inc. Transaction data structure for process communications among network-distributed applications
US6721777B1 (en) 2000-05-24 2004-04-13 Sun Microsystems, Inc. Modular and portable deployment of a resource adapter in an application server
US6832238B1 (en) * 2000-05-24 2004-12-14 Sun Microsystems, Inc. Local transaction management
AU2001264944A1 (en) 2000-05-25 2001-12-03 Transacttools, Inc. A method, system and apparatus for establishing, monitoring, and managing connectivity for communication among heterogeneous systems
JP4757370B2 (en) * 2000-05-30 2011-08-24 住友化学株式会社 Epitaxial substrate manufacturing method
US6687848B1 (en) 2000-05-31 2004-02-03 Sun Microsystems, Inc. Techniques for preventing information loss in a business to business message in an enterprise computer system
US6959340B1 (en) * 2000-05-31 2005-10-25 Sun Microsystems, Inc. Platform independent business to business messenger in an enterprise computer system
US7127704B2 (en) 2000-06-02 2006-10-24 Sun Microsystems, Inc. Interactive software engineering tool with support for embedded lexical contexts
US6993743B2 (en) 2000-06-03 2006-01-31 Sun Microsystems, Inc. Method and apparatus for developing enterprise applications using design patterns
US6675227B1 (en) * 2000-06-05 2004-01-06 International Business Machines Corporation Method for providing a service implementation for both EJB and non-EJB environments
US6874143B1 (en) 2000-06-21 2005-03-29 Microsoft Corporation Architectures for and methods of providing network-based software extensions
US6836883B1 (en) 2000-06-21 2004-12-28 Microsoft Corporation Method and system for compiling multiple languages
US20020194267A1 (en) 2000-06-23 2002-12-19 Daniel Flesner Portal server that provides modification of user interfaces for access to computer networks
US6721779B1 (en) 2000-07-07 2004-04-13 Softwired Ag Messaging proxy system
US20030037181A1 (en) * 2000-07-07 2003-02-20 Freed Erik J. Method and apparatus for providing process-container platforms
US20020143960A1 (en) 2000-08-02 2002-10-03 Erez Goren Virtual network generation system and method
US20020038450A1 (en) * 2000-08-03 2002-03-28 International Business Machines Corporation Method and system to run stored procedures as workflow activity implementations
US6684388B1 (en) 2000-08-22 2004-01-27 International Business Machines Corporation Method for generating platform independent, language specific computer code
US6732237B1 (en) 2000-08-29 2004-05-04 Oracle International Corporation Multi-tier caching system
FR2813471B1 (en) 2000-08-31 2002-12-20 Schneider Automation COMMUNICATION SYSTEM FOR AUTOMATED EQUIPMENT BASED ON THE SOAP PROTOCOL
WO2002019097A1 (en) 2000-09-01 2002-03-07 International Interactive Commerce, Ltd. System and method for collaboration using web browsers
US6823495B1 (en) 2000-09-14 2004-11-23 Microsoft Corporation Mapping tool graphical user interface
US6560769B1 (en) 2000-09-28 2003-05-06 Unisys Corporation Computer-implemented method for generating a UML representation from JAVA source code
US7069507B1 (en) 2000-09-29 2006-06-27 Microsoft Corporation Event routing model for an extensible editor
US6889244B1 (en) 2000-10-31 2005-05-03 Hewlett-Packard Development Company, L.P. Method and apparatus for passing messages using a fault tolerant storage system
IE20010964A1 (en) 2000-11-03 2002-05-29 Wilde Technologies Ltd A software development process
AU2002239620A1 (en) 2000-11-06 2002-05-27 Terry Bernard Young Electronic markets business interchange system and metheo
US20020078365A1 (en) 2000-12-15 2002-06-20 International Business Machines Corporation Method for securely enabling an application to impersonate another user in an external authorization manager
US7275220B2 (en) 2000-12-22 2007-09-25 Epic Systems Corporation System and method for a seamless user interface for an integrated electronic health care information system
US7174534B2 (en) 2001-01-22 2007-02-06 Symbol Technologies, Inc. Efficient system and method for running and analyzing multi-channel, multi-modal applications
US20020161826A1 (en) 2001-01-25 2002-10-31 Carlos Arteaga System and method for remote communication transactions
US20020165936A1 (en) 2001-01-25 2002-11-07 Victor Alston Dynamically branded web sites
US6567738B2 (en) 2001-01-30 2003-05-20 Ford Global Technologies, Llc Fueling control system
US6757689B2 (en) 2001-02-02 2004-06-29 Hewlett-Packard Development Company, L.P. Enabling a zero latency enterprise
US7957999B2 (en) 2001-02-13 2011-06-07 American Express Travel Related Services Company, Inc. Electronic acquisition system and method
US7111243B1 (en) 2001-03-02 2006-09-19 Oracle International Corporation Customization of tab-order functionality in internet applications
US7184967B1 (en) 2001-03-06 2007-02-27 Microsoft Corporation System and method utilizing a graphical user interface of a business process workflow scheduling program
US20030004746A1 (en) 2001-04-24 2003-01-02 Ali Kheirolomoom Scenario based creation and device agnostic deployment of discrete and networked business services using process-centric assembly and visual configuration of web service components
US7472399B2 (en) * 2001-04-26 2008-12-30 Iona Technologies, Plc Method and system for a client invoking on an interface defined in a first notation to invoke an object having an interface defined in a second notation
US6983328B2 (en) 2001-05-18 2006-01-03 Hewlett-Packard Development Company, L.P. Trusted internet clipboard
US20020184145A1 (en) 2001-05-31 2002-12-05 Sun Microsystems, Inc. Methods and system for integrating XML based transactions in an electronic invoice presentment and payment environment
US7152090B2 (en) * 2001-06-01 2006-12-19 Sun Microsystems, Inc. Metadata-aware enterprise application integration framework for application server environment
US20020194244A1 (en) 2001-06-01 2002-12-19 Joan Raventos System and method for enabling transaction-based service utilizing non-transactional resources
US7594267B2 (en) 2001-06-14 2009-09-22 Cisco Technology, Inc. Stateful distributed event processing and adaptive security
US6687702B2 (en) 2001-06-15 2004-02-03 Sybass, Inc. Methodology providing high-speed shared memory access between database middle tier and database server
US6976086B2 (en) 2001-06-18 2005-12-13 Siemens Business Services, Llc Systems and methods to facilitate a distribution of information via a dynamically loadable component
US20030014439A1 (en) 2001-06-20 2003-01-16 International Business Machines Corporation Defining a markup language representation for state chart data
EP1410258A4 (en) * 2001-06-22 2007-07-11 Inc Nervana System and method for knowledge retrieval, management, delivery and presentation
US7085286B2 (en) * 2001-06-29 2006-08-01 International Business Machines Corporation Stateful business-to-business protocol exchange
US7356803B2 (en) 2001-07-02 2008-04-08 Bea Systems, Inc. Annotation based development platform for asynchronous web services
US6754884B1 (en) 2001-07-02 2004-06-22 Bea Systems, Inc. Programming language extensions for processing XML objects and related applications
US6799718B2 (en) 2001-07-10 2004-10-05 Borland Software Corp. Development assistance for mixed-language sources
US7117504B2 (en) 2001-07-10 2006-10-03 Microsoft Corporation Application program interface that enables communication for a network software platform
US7210094B2 (en) 2001-07-11 2007-04-24 International Business Machines Corporation Method and system for dynamic web page breadcrumbing using javascript
US6915519B2 (en) 2001-07-12 2005-07-05 International Business Machines Corporation Pluggable JMS providers in a J2EE server
US20030018661A1 (en) 2001-07-19 2003-01-23 Darugar Parand Tony XML smart mapping system and method
US20030046266A1 (en) * 2001-07-26 2003-03-06 Ward Mullins System, method and software for creating or maintaining distributed transparent persistence of complex data objects and their data relationships
US7054858B2 (en) 2001-08-01 2006-05-30 Oic Acquisition Corporation System and method for retrieval of objects from object to relational mappings
US20030028579A1 (en) 2001-08-06 2003-02-06 Kulkarni Vinay Vasant Process for component-based application development
US7367028B2 (en) 2001-08-14 2008-04-29 National Instruments Corporation Graphically deploying programs on devices in a system
US20030037153A1 (en) * 2001-08-16 2003-02-20 Ouchi Norman Ken Information transfer protocol system and private exchange
US20030043191A1 (en) * 2001-08-17 2003-03-06 David Tinsley Systems and methods for displaying a graphical user interface
US7356837B2 (en) 2001-08-29 2008-04-08 Nader Asghari-Kamrani Centralized identification and authentication system and method
US7035944B2 (en) * 2001-09-19 2006-04-25 International Business Machines Corporation Programmatic management of software resources in a content framework environment
US6985939B2 (en) * 2001-09-19 2006-01-10 International Business Machines Corporation Building distributed software services as aggregations of other services
US6980979B2 (en) * 2001-09-19 2005-12-27 Sun Microsystems, Inc. Method and apparatus for customizing Java API implementations
US7107578B1 (en) 2001-09-24 2006-09-12 Oracle International Corporation Techniques for debugging computer programs involving multiple programming languages
AU2002343424A1 (en) 2001-09-28 2003-04-14 Bluesocket, Inc. Method and system for managing data traffic in wireless networks
US20030074467A1 (en) * 2001-10-11 2003-04-17 Oblak Sasha Peter Load balancing system and method for data communication network
CA2358681C (en) 2001-10-12 2008-01-15 Ibm Canada Limited-Ibm Canada Limitee Resource adapter and integrated development environment
US7552222B2 (en) 2001-10-18 2009-06-23 Bea Systems, Inc. Single system user identity
US7089568B2 (en) * 2001-10-26 2006-08-08 Hitachi, Ltd. Program control method, computer system, control program, and storage medium storing the control program
EP2309384A1 (en) * 2001-10-29 2011-04-13 Accenture Global Services GmbH A generic connector between vitria and an EJB compliant API for an application
US8156471B2 (en) 2001-11-09 2012-04-10 Oracle International Corporation Multi-language execution method
US20030110446A1 (en) * 2001-12-10 2003-06-12 Sun Microsystems, Inc. Object class for facilitating conversion between Java and XML
US6950872B2 (en) 2001-12-19 2005-09-27 Sun Microsystems, Inc. Methods and systems for facilitating message exchange between networked computing entities
US7240331B2 (en) 2002-01-16 2007-07-03 Xerox Corporation Bi-valuation of programming statements
US8151003B2 (en) * 2002-02-05 2012-04-03 International Business Machines Corporation System and method for routing data by a server
US7516447B2 (en) * 2002-02-22 2009-04-07 Bea Systems, Inc. Methods and apparatus for building, customizing and using software abstractions of external entities
US20030196168A1 (en) * 2002-04-10 2003-10-16 Koninklijke Philips Electronics N.V. Method and apparatus for modeling extensible markup language (XML) applications using the unified modeling language (UML)
US7412495B2 (en) 2002-04-26 2008-08-12 Sun Microsystems, Inc. Method, system, and article of manufacture for a server side application
US6804686B1 (en) 2002-04-29 2004-10-12 Borland Software Corporation System and methodology for providing fixed UML layout for an object oriented class browser
WO2003093964A1 (en) * 2002-05-01 2003-11-13 Bea Systems, Inc. Enterprise application platform
US20030233631A1 (en) * 2002-06-13 2003-12-18 Ambrose Curry Web services development method
US7434207B2 (en) 2002-07-02 2008-10-07 Microsoft Corporation Floating debugger
US7720910B2 (en) * 2002-07-26 2010-05-18 International Business Machines Corporation Interactive filtering electronic messages received from a publication/subscription service
US7043722B2 (en) 2002-07-31 2006-05-09 Bea Systems, Inc. Mixed language expression loading and execution methods and apparatuses
US7523174B2 (en) 2002-10-15 2009-04-21 International Business Machines Corporation Dynamic portal assembly
KR100501410B1 (en) 2002-11-27 2005-07-18 한국전자통신연구원 System and method of generating EJB component from reusable business logic in servlet
US7448024B2 (en) 2002-12-12 2008-11-04 Bea Systems, Inc. System and method for software application development in a portal environment
US7650591B2 (en) * 2003-01-24 2010-01-19 Bea Systems, Inc. Marshaling and un-marshaling data types in XML and Java
US7076772B2 (en) 2003-02-26 2006-07-11 Bea Systems, Inc. System and method for multi-language extensible compiler framework
US7096422B2 (en) 2003-02-28 2006-08-22 Microsoft Corporation Markup language visual mapping
US20040225995A1 (en) 2003-02-28 2004-11-11 Kyle Marvin Reusable software controls
US20040260715A1 (en) * 2003-06-20 2004-12-23 Mongeon Brad A. Object mapping across multiple different data stores
US7739223B2 (en) 2003-08-29 2010-06-15 Microsoft Corporation Mapping architecture for arbitrary data models

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6348970B1 (en) * 1998-04-29 2002-02-19 Qwest Communications Int'l., Inc. Apparatus and method for interfacing a computer network to a facsimile machine
US6345283B1 (en) * 1998-07-20 2002-02-05 New Technologies Armor, Inc. Method and apparatus for forensic analysis of information stored in computer-readable media
US6360221B1 (en) * 1999-09-21 2002-03-19 Neostar, Inc. Method and apparatus for the production, delivery, and receipt of enhanced e-mail

Also Published As

Publication number Publication date
US20040006663A1 (en) 2004-01-08
US7257645B2 (en) 2007-08-14
AU2003237146A1 (en) 2003-11-17
US20070198467A1 (en) 2007-08-23
US7840532B2 (en) 2010-11-23

Similar Documents

Publication Publication Date Title
US7840532B2 (en) System and method for storing large messages
EP3320670B1 (en) Method and apparatus for pushing data in a content-centric networking (ccn) network
EP0950969B1 (en) Method and system for out-tasking conversions of message attachments
US6021427A (en) Method and system for preventing routing maelstrom loops of automatically routed electronic mail
US20040010543A1 (en) Cached resource validation without source server contact during validation
US7035902B1 (en) Method, article of manufacture and apparatus for processing an electronic mail document
US10110528B2 (en) System and method for enabling an external-system view of email attachments
US8135750B2 (en) Efficiently describing relationships between resources
US20070180035A1 (en) E-mail attachment selectable download
US20060259558A1 (en) Method and program for handling spam emails
US20020198944A1 (en) Method for distributing large files to multiple recipients
US8321381B2 (en) Facilitating a sender of email communications to specify policies with which the email communication are to be managed as a record
GB2340269A (en) Message store
CA2448423A1 (en) Method and system for tracking receipt of electronic message
US6920476B2 (en) Messaging system for computers
US7716290B2 (en) Send by reference in a customizable, tag-based protocol
US20080071865A1 (en) Method, System and Program Product Providing Compact Storage For Electronic Messages
EP0953907A2 (en) Method and apparatus for high performance access to data in a message store
WO2002008852A2 (en) System and method for intelligent transmission of digital content embedded in electronic mail messages
US20060277458A9 (en) Object persister
US20060265455A1 (en) Automatic recovery from failures of messages within a data interchange
CN104077363B (en) Mail server and its method for carrying out mail full-text search
US20070112848A1 (en) Method and system for concurrently processing multiple large data files transmitted using a multipart format
JPH06284145A (en) Electronic mail system
JP2000215117A (en) Mail server, electronic mail storing method, and medium recorded with program for electronic mail storage

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 NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VC 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 BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK 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
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP