From: Andrey Mirtchovski <aam396@mail.usask.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] setup?
Date: Fri, 21 Jul 2000 10:36:53 -0600 [thread overview]
Message-ID: <39787C25.CD236E3B@mail.usask.ca> (raw)
In-Reply-To: <20000721113238.A429@crdevilb.bresnanlink.net>
Colin DeVilbiss wrote:
>
> (I have some experience with unix sockets, but I have not written any
> plan9 networking software; for that matter, s/networking //.)
Oh, networking in plan9 is fun! It's mostly a matter of composing a string
to pass to dial() and after that it's all peachy and creamy. I have a
200-line irc client done in no time, which is now being slowly designed
into a filesystem so that it will *fit* plan9 better...
Sockets experience doesn't seem to matter much -- everything is nicely
'encapsulated' and the 'paradigms' are of a higher level.
andrey
next prev parent reply other threads:[~2000-07-21 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-21 15:05 Russ Cox
2000-07-21 15:32 ` Colin DeVilbiss
2000-07-21 16:36 ` Andrey Mirtchovski [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-24 3:02 okamoto
2000-07-21 18:44 jmk
2000-07-21 18:19 Russ Cox
2000-07-21 1:19 Colin DeVilbiss
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=39787C25.CD236E3B@mail.usask.ca \
--to=aam396@mail.usask.ca \
--cc=9fans@cse.psu.edu \
/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).