Reduce cost of payload fanout, or pass-on by removing data transfer requirements
Original Publication Date: 2004-Apr-22
Included in the Prior Art Database: 2004-Apr-22
This disclosure shows a technique for an application program to pass on a data payload to one or more destination, without having to transfer the payload to the application. In this way the cost to do the work is reduced.
Reduce cost of payload fanout, or pass -on by removing data transfer requirements
There are many applications that route a data payload to different applications, for example a publish/subscribe (where the payload could be sent to many destinations) or a routing application where the payload is sent to just one destination. These applications do not look into the payload, they just pass it on.
There is a cost in moving a payload to an application, especially as the identical payload is passed back almost immediately. This article shows how we can reduce this cost by eliminating the transfer of the payload to the application, and the one or more transfers of the payload from the application.
A broadcast application may not be interested in the contents of the payload - its role is just to broadcast it.
The following shows how the process works: Broadcast Application
This requests the service provider to get the payload indicating a no-data-transfer request. The system remembers where the data came from.
For each destination call the service provider to send the data using 'last data read' to the destination. This send 'last data read' uses the saved payload used by the previous get request.
This way we eliminate the need to transfer the data to the broadcast application buffers, and from the application buffers a few moments later. This will reduce the CPU requirements, and virtual storage used.
If required the payload can be transferred to the application, then u...