From: Chris McGee <newton688@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] libtask
Date: Tue, 18 Oct 2016 17:43:49 -0400 [thread overview]
Message-ID: <A4D3FC27-40CF-4F68-B691-146C52066B47@gmail.com> (raw)
In-Reply-To: <CAJSxfmJdrPDbyCMMLtdSzVEEkSPhamNiv7F2HO-kkh6KgQgMGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Yeah, I saw that and it made me chuckle, especially once I discovered the recursive reflection.
It's reasonably easy to program in it. I know that it can handle 16 bit 44.1 kHz stereo pcm streaming over a network. Does that it "performing?"
Chris
>
> Reading the description of the go-p9p, it says "A modern, performant 9P library for Go.". I'm guessing "modern" refers to being implemented in Go. Any pointers on how performance was measured or what it was measured against?
>
>
>
>> On Tue, Oct 18, 2016 at 11:32 AM Chris McGee <newton688@gmail.com> wrote:
>> If you're interested in Go, this 9p library has worked reasonably well for my servers.
>>
>> https://github.com/docker/go-p9p
>>
>>
>>> On Oct 18, 2016, at 1:31 PM, Iruatã Souza <iru.muzgo@gmail.com> wrote:
>>>
>>> https://github.com/iru-/lua9p
>>
>>>
>>>
>>>> On Thu, Oct 13, 2016 at 3:47 PM, yy <yiyu.jgl@gmail.com> wrote:
>>>>> On 13 October 2016 at 18:03, Steve Simon <steve@quintile.net> wrote:
>>>>> Anyone written or ported a small simple 9p library;
>>>>
>>>> As part of a GSoC project I wrote
>>>> https://bitbucket.org/yiyus/devwsys-prev/src/tip/libninep/ (man pages
>>>> can be found in the same repo). There is a ninepserver but not a
>>>> ninepclient because the only client I wrote was to be used with p9p,
>>>> so I was using 9pclient(3), but it should be relatively easy to write
>>>> one if you need it.
>>>>
>>>>
>>>> --
>>>> - yiyus || JGL .
>>>>
>>>
[-- Attachment #2: Type: text/html, Size: 4728 bytes --]
prev parent reply other threads:[~2016-10-18 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 16:03 Steve Simon
2016-10-13 16:29 ` Stanley Lieber
2016-10-13 16:39 ` Sigrid Haflinadóttir
2016-10-13 17:25 ` michaelian ennis
2016-10-13 17:29 ` michaelian ennis
2016-10-13 18:47 ` yy
2016-10-18 17:31 ` Iruatã Souza
2016-10-18 18:32 ` Chris McGee
2016-10-18 20:54 ` Skip Tavakkolian
2016-10-18 21:43 ` Chris McGee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A4D3FC27-40CF-4F68-B691-146C52066B47@gmail.com \
--to=newton688@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).