Browse Prior Art Database

A Communication System for Enabling Application-Specified Message-Loss Handling

IP.com Disclosure Number: IPCOM000123726D
Original Publication Date: 1999-Apr-01
Included in the Prior Art Database: 2005-Apr-05
Document File: 2 page(s) / 80K

Publishing Venue

IBM

Related People

Negishi, Y: AUTHOR [+3]

Abstract

A program is disclosed that is a communication system with an API that enables an application to specify for each message if the message is losable or not. Identity of losable messages can be specified explicitly using message identifiers or implicitly, e.g. on execution of "if condition then" statement and condition may be reception of a message or in general change in value of any predicate.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

A Communication System for Enabling Application-Specified Message-Loss
Handling

   A program is disclosed that is a communication system with
an API that enables an application to specify for each message if
the message is losable or not.  Identity of losable messages can be
specified explicitly using message identifiers or implicitly, e.g. on
execution of "if condition then" statement and condition may be
reception of a message or in general change in value of any
predicate.

   Following four are example APIs provided by our
system.  (The detail depends on each programming language to be
used.)
  (a) A sender can explicitly specify that a specific message
      in a set of messages M is losable by executing
      "Send(M, ...):losable."
  (b) Receiver or Sender can implicitly specify a set of messages
      as lost, e.g. by executing "if phase change then
      messages of last phase are losable."
  (c) Receiver can execute a receive command "receive(S):90%"
      implying 90% of set S are to be received and the
      rest can be declared lost.

   In existing systems, an application either uses loss-less
communication system (such as TCP/IP), thus incurring high cost of
implementing loss-less communication system even if message loss is
OK, or handles loss of messages by itself, thus required separate
efforts for each application.

   Loss-less communication systems introduce an unnecessary
overhead because they cannot allow the message-loss, even if
application does not particularly need loss-lessness.  On the other
hand, It is difficult for programmers to implement a protocol for
handling loss of messages by at application level and efforts need to
be repeated for each application.

   In our system, applications can handle loss of messages
without implementing a new protocol, it can take...