9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Fri, 12 Nov 2010 15:23:40 -0500	[thread overview]
Message-ID: <aaf2829bd720b9602c745f96c4dc1b0a@coraid.com> (raw)
In-Reply-To: <AANLkTi=tiVM-irt0L-bqiM-jmpAQ1TU8sz-C2zL9bFFy@mail.gmail.com>

> And, finally, errno and errstr. Plan 9 speaks strings, Unix integers,
> Windows strings IIRC. The solution for unix clients was reverse
> mapping of errstr to errno, which has not worked well for me. I'd
> still prefer the format I used before:
> sprint(rmsg.error, "%d:%s", errno, errstr);
> and let the client figure out which of these two things it wants.
> Obviously useless for Plan 9 servers but very useful for *nix
> clients/servers, which only want to talk errno. Even if the Plan 9
> client sees an errstr in the number:message format, that could be
> helpful to users.

since plan 9 assumes that strings are null-terminated but
9p has explicit rle, one could send uids/errorno after the 0,
but before the rle says the string is done.

sleezy, and hackish, but it should work.

also, one can always support many extensions by doing
the following
(a) extensions are [a-zA-Z]
(b) all extensions start with "."

then you can check for the existence of an extension
with
	if(strstr(version, ".myextension") != nil)
		extensions |= Myextension;

and
	P92000.l.op.xyz.pdq

will be legal.

- erik



  reply	other threads:[~2010-11-12 20:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 21:13 erik quanstrom
2010-11-09  3:37 ` erik quanstrom
2010-11-09 17:41   ` David Leimbach
2010-11-09 17:51     ` erik quanstrom
2010-11-10  0:37       ` erik quanstrom
2010-11-10  1:49         ` Russ Cox
2010-11-10  6:46           ` erik quanstrom
2010-11-10 14:31             ` Russ Cox
2010-11-12  3:35               ` Noah Evans
2010-11-12  5:34                 ` erik quanstrom
2010-11-12  5:46                   ` Noah Evans
2010-11-12  6:03                   ` Noah Evans
2010-11-12  6:19                     ` Russ Cox
2010-11-12  6:25                       ` Noah Evans
2010-11-12  9:07                       ` EBo
2010-11-12 15:12                         ` David Leimbach
2010-11-12 15:19                       ` Eric Van Hensbergen
2010-11-12 15:35                         ` erik quanstrom
2010-11-12 15:55                         ` Russ Cox
2010-11-12 16:22                           ` Eric Van Hensbergen
2010-11-12 19:55                             ` ron minnich
2010-11-12 20:23                               ` erik quanstrom [this message]
2010-11-12 20:31                                 ` Eric Van Hensbergen
2010-11-12 20:37                                   ` ron minnich
2010-11-12 20:30                               ` Eric Van Hensbergen
2010-11-12 20:41                                 ` ron minnich
2010-11-12 22:15                                   ` Eric Van Hensbergen
2010-11-12 22:20                                     ` ron minnich
2010-11-12 22:36                                       ` Russ Cox
2010-11-13  8:31                                       ` tlaronde
2010-11-13 23:42                                         ` Dave Eckhardt
2010-11-14 22:49                                       ` Nathaniel W Filardo
2010-11-15 16:22                                         ` erik quanstrom
2010-11-15 17:40                                           ` Nathaniel W Filardo
2010-11-15 17:50                                   ` John Floren
2010-11-12 21:12                               ` Russ Cox
2010-11-09 18:08     ` yy
2010-11-09 19:17     ` Bakul Shah
2010-11-09 19:27     ` Russ Cox

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=aaf2829bd720b9602c745f96c4dc1b0a@coraid.com \
    --to=quanstro@labs.coraid.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).