The RSF system is a real-time reminder-based subscriber-feed system which allows a web server to track a person's access to their feed subscriptions. The feed messages are based on our reminder xml schema (patent pending). The RSF system uses the same tracking mechanism as the RCAS system; and is essentially an extension to RCAS.

The RSF system is developed on top of an HTTP server, which is able to send PUT requests, to a user's desktop. The user's desktop must be running an HTTP server and/or plugin, which can send and receive the reminder-based feed messages. The sending server tracks every link, which is clicked or accessed by the user; allowing the originating server to track every query made to a desktop or  internet accessible content.

The origin and content of every query is tracked, based on keywords used and content requested. The information associated with each query, which is used by RSF, is taken from the web server, which may or not be a content-enabled one. If the web server does not provide content information; then, RSF generates its own, based on the data provided.

RSF uses the display attributes of the message/reminder, to summarize visually the content of the message, in this case the feed message. When a user clicks on the visual summary, the full content of the feed is then presented to the user. The full content can be a link to the originating server, or embedded script, html, or animation file, such as flash or silverlight. The link itself can be a music file, a software package, book reviews, etc..

A plugin which understands our reminder feed schema (patent pending), must be running on the user's desktop; it must also be able to send HTTP get requests to the originating server. The plugin  must perform a handshake with the originating server (with or without  SALT or SSL), every time a user turns-on their computer and their internet access. The handshake is required by RSF so that feed updates can be sent to the user's desktop or retrieved from the server. The RSF system also regularly scans the internet/network, to initiate handshakes with subscribers who may be online. The handshake may contain additional information regarding which ports to access on the server, for downloads.

An adjunct to this patent is the use of our HTTP SALT protocol to both secure the message exchanges, and to identify the recipient of the feed messages by RSF. The plugin can perform the handshake through a UDP or TCP port. The server can broadcast the feed messages to a reserved audience, which is identified by internet network masking or subdomain addressing, or by a list of subscribers or users, identified as clubs (patent pending) or account list.

An second adjunct to this patent is the use of display attributes which are used to present a visual summary of the content of the transmitted message/reminder to the user. The display attributes can be a link to an animation file, a set or sequence of icons, animated or not, seen as pictograms. The animation file or icons can be embedded inline in the message.

A third adjunct to this patent is the option of using another authentication protocol, instead of the SALT protocol, when sending the feed messages. The most obvious alternatives to our SALT protocol are the OpenID protocol or HTTP Cookies and Authorization headers.

A fourth adjunct to this patent is the requirement of having a dynamic naming service alias a fully qualified domain name (FQDN) to your host computer, as it is connected to the Internet, if a static IP address is not provided.

Patent Pending

Tsert.inc/Tsert.Com