Difference: TrbNetStreamingAPI (r3 vs. r2)

Trbnet Streaming API

A streaming API allows an application to be inserted into the data stream. There it can fullfill two different tasks: It can simply preprocess the data stream and then send it on with some changes. An extended version of this api can also contain an additional network connection. In this mode, the data that is received can be coupled out of the main network and is sent on this separated link to another receiver. On the original stream only a small transfer with some status information is kept.

Each streaming API is connected to only one data channel, all others channels are not affected by its operation. On the channel it is connected to, it acts as an endpoint to be able to receive incoming transfers. This endpoint always answers with a short transfer.

The users streaming application has three ports it is connected to: the incoming init data (this is read only and is terminated automatically), the incoming reply data and the reply data output. In the case of a design to couple out data, the additional data port is implemented by the user application. (There will be some prewritten code to allow the user to not care about this)

An extended streaming API included inside a hub

-- JanMichel - 14 Mar 2008

streaming_api.pngpngstreaming_api.pngmanage 13.9 K 14 Mar 2008 - 08:10JanMichel An extended streaming API included inside a hub

View topic | View difference side by side | History: r3 < r2 < r1 | More topic actions
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)