Browse Prior Art Database

Routing Forum Appends Receied via Monitored Filtering Method

IP.com Disclosure Number: IPCOM000106081D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 102K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+3]

Abstract

This invention is built upon and directly related in [*]. Currently, no method exists for a forum user to receive forum appended replies which directly relate to a selected topic and have those replies converted, translated and/or routed via various predetermined methods. The term topic, within this invention, is described as the text within the subject line of an append.

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

Routing Forum Appends Receied via Monitored Filtering Method

      This invention is built upon and directly related in [*].
Currently, no method exists for a forum user to receive forum
appended replies which directly relate to a selected topic and have
those replies converted, translated and/or routed via various
predetermined methods.  The term topic, within this invention, is
described as the text within the subject line of an append.

      Conference disk appends have "Subject:" lines which are meant
to indicate the topic of conversation.  All replies to an append
carry this line by default.  The user creating the originating append
fills in the "Subject:"  line according to preference.  This is the
append's topic of conversation.  Users may append a reply to either
the originating append or to another user's reply.  Each append in
the heirarchy contains the same original "Subject:" line.  Also, all
replies carry a "Ref:" line which indicates which append in the topic
of conversation is being referenced.  This line contains userid,
node, time and date information for the referenced append.  Using
this information the entire reply history of an originating append
can be determined.

      The user interfaces with the Append Handler on the local system
to create Append Filters and subsequently receive appends.  The
Append Handler works with the Append Manager on the conferencing
system through the use of Append Filters.

      When appends arrive in a user's reader the Append Handler
determines the active Append Filter which led to the sending of the
append.  This filter is then used to determine the conversion,
translation and/or routing specifications for the received append.

      The configuration parameters are set during Filter creation but
can also be updated at some later date.  Configuration parameters are
interpreted by the Append Handler and control the conversion,
translation and routing characters for the append.  This involves the
use of various methods for routing forum appended replies.  The
conversion, translation and routing processes work together to
perform such tasks as text to voice for phone messages, fascimile
transmissions, printer hardcopy and beeper notification, to name a
few.

      For example, a user (JOHNDOE) places an append on the WHEREIS
FORUM.  The append is requesting from all forum followers a response
if the reader knows their state capitol, state flower, state animal
and date of annexation into the United States.  The user will be in
class during the following work week.  In order to receive all reply
appends generated during the weekend and the next week the user
decides to have all the responses placed into his phone messaging
system.  To do this an Append Filter is created using the Append
Handler and sent to Append...