From mboxrd@z Thu Jan 1 00:00:00 1970 References: <86iojlmin5.fsf@cmarib.ramside> In-Reply-To: Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-DFF2896B-2DF4-49E1-B948-3B831DDC22A7 Message-Id: <6D496128-1E65-46FD-826E-3E2D2D3B51FF@lsub.org> Content-Transfer-Encoding: 7bit From: "Fran. j. Ballesteros " Date: Wed, 15 Oct 2014 19:14:58 +0200 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] server push in 9P protocol Topicbox-Message-UUID: 1d49d366-ead9-11e9-9d60-3106f5b1d025 --Apple-Mail-DFF2896B-2DF4-49E1-B948-3B831DDC22A7 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable the ideas are in Clive, but the code won't run for 9p or plan 9.=20 but I think I copied somewhere (sources)? ix which was ok for a plan9 world,= but experimental.=20 > El 15/10/2014, a las 18:55, Skip Tavakkolian e= scribi=C3=B3: >=20 > search 9fans archives for 9P streaming. i think nemo and lsub crew had exp= erimented with some variation i believe. i'm not sure if it is brought into= Clive, their new effort. >=20 >=20 >> On Wed, Oct 15, 2014 at 8:56 AM, wrote: >> Hello, >>=20 >> I'm wondering if there is any way to do server push using the 9P >> protocol. I'm trying to imagine use of 9P for applications such as data >> acquisition. One example might be caputing MIDI messages from digital >> musical instruments. >>=20 >> As I understand the protocol, if an instrument served MIDI over 9P, >> every MIDI message would have to be explicitly requested with a Tread. >> And the instrument would have to wait for a Tread in order to send data. >> If the instrument (server) sent more than one Rread with the same tag, >> that would be a violation of the protocol. >>=20 >> It might be possible to reverse roles: for the instrument to act as a 9P >> client and treat the MIDI host as a 9P server. In that case, each MIDI >> message could take the form of a Twrite to the MIDI host. But that >> would generate a series of Rwrites back from the host to the instrument, >> which would be unnecessary and have to be ignored. >>=20 >> Another example might be isochronous data streams, such as video >> captured at a fixed framerate from a video capture device. Having to >> send the same Tread or Rread 30x/second seems silly. >>=20 >> So, is there any way use 9P in a server-push mode, where the server >> spits out a stream of data to be captured? >>=20 >> Thanks! >=20 --Apple-Mail-DFF2896B-2DF4-49E1-B948-3B831DDC22A7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
the ideas are in Clive, but the code
won't run for 9p or plan 9. 

but I th= ink I copied somewhere (sources)? ix which was ok for a plan9 world, but exp= erimental. 

El 15/10/2014, a las 18:55, Skip Tavakkolian &= lt;skip.tavakkolian@gmail.com<= /a>> escribi=C3=B3:


On Wed, Oct 15, 2014 at 8:56 AM, <s= miley@icebubble.org> wrote:
H= ello,

I'm wondering if there is any way to do server push using the 9P
protocol.  I'm trying to imagine use of 9P for applications such as dat= a
acquisition.  One example might be caputing MIDI messages from digital<= br> musical instruments.

As I understand the protocol, if an instrument served MIDI over 9P,
every MIDI message would have to be explicitly requested with a Tread.
And the instrument would have to wait for a Tread in order to send data.
= If the instrument (server) sent more than one Rread with the same tag,
that would be a violation of the protocol.

It might be possible to reverse roles: for the instrument to act as a 9P
= client and treat the MIDI host as a 9P server.  In that case, each MIDI=
message could take the form of a Twrite to the MIDI host.  But that
= would generate a series of Rwrites back from the host to the instrument,
= which would be unnecessary and have to be ignored.

Another example might be isochronous data streams, such as video
captured at a fixed framerate from a video capture device.  Having to send the same Tread or Rread 30x/second seems silly.

So, is there any way use 9P in a server-push mode, where the server
spits out a stream of data to be captured?

Thanks!


= --Apple-Mail-DFF2896B-2DF4-49E1-B948-3B831DDC22A7--