Slashdot Mirror
Multi-Channel Communication Patent Up For Sale
OTDR alerts us to the latest software patent stupidity in the news as patent number 6,418,462, "methods allowing clients to perform tasks through a sideband communication channel, in addition to the main communication channel between a client and server," snubs its nose at AJAX, ftp, and decades of prior art and goes on sale next month in San Fransisco. "Singled out are AJAX mashups including Google Maps and Gmail, and Microsoft 'Live'... Also in the frame are Amazon's S3 and EC2 and clusters from Microsoft, VMware, and Oracle. eBay's Skype, Napster, and Microsoft's Groove are also listed as potentially infringing on the patent in P2P."
Is this really the patent?
My reading is that it doesn't really claim what TFA is claiming it does.
This patent seems to be patenting a process where many unrelated clients connect to a supposedly lightweight server and distributes workloads among those clients via a sideband channel. That's not my understanding of how Ajax works.
It seems to me that it suffers from the same issues that many distributed computing platforms suffer from which is that you get free CPU at the expense of a great deal of bandwidth so it's only useful for a very limited sets of workloads. In this case I can't really imagine what you'd use it for.
Forget SETI at home look at PVM. First release 1989 !!
http://en.wikipedia.org/wiki/Parallel_Virtual_Machine
Description here
http://www.netlib.org/pvm3/book/node17.html
Main channel is to pvmd. "backchannel" is the process to process communication.
--
The PVM system is composed of two parts. The first part is a daemon , called pvmd3 and sometimes abbreviated pvmd , that resides on all the computers making up the virtual machine. (An example of a daemon program is the mail program that runs in the background and handles all the incoming and outgoing electronic mail on a computer.) Pvmd3 is designed so any user with a valid login can install this daemon on a machine. When a user wishes to run a PVM application, he first creates a virtual machine by starting up PVM. (Chapter 3 details how this is done.) The PVM application can then be started from a Unix prompt on any of the hosts. Multiple users can configure overlapping virtual machines, and each user can execute several PVM applications simultaneously.
--
The general paradigm for application programming with PVM is as follows. A user writes one or more sequential programs in C, C++, or Fortran 77 that contain embedded calls to the PVM library. Each program corresponds to a task making up the application. These programs are compiled for each architecture in the host pool, and the resulting object files are placed at a location accessible from machines in the host pool. To execute an application, a user typically starts one copy of one task (usually the ``master'' or ``initiating'' task) by hand from a machine within the host pool. This process subsequently starts other PVM tasks, eventually resulting in a collection of active tasks that then compute locally and exchange messages with each other to solve the problem. Note that while the above is a typical scenario, as many tasks as appropriate may be started manually. As mentioned earlier, tasks interact through explicit message passing, identifying each other with a system-assigned, opaque TID.
--