9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Uriel <uriel@berlinblue.org>
To: 9front@googlegroups.com
Subject: Re: todo
Date: Fri, 1 Apr 2011 03:24:16 -0700	[thread overview]
Message-ID: <AANLkTi=gN9j_BQM3ya0KiP6r-xcHRMgZuNCPde-hGkkc@mail.gmail.com> (raw)
In-Reply-To: <3adde944e6b9688e2492230f017e56a8@gmx.de>

We already went down the path of new Tmessages and new Tversions with
.u, and it was a huge fucking nightmare.

I don't see what is so bad about an alternative attach name for this
kinds of operations, somebody did something like that for file change
notification and other things, it was really neat.

uriel

On Fri, Apr 1, 2011 at 3:18 AM,  <cinap_lenrek@gmx.de> wrote:
> as i read the manpage to Tversion, the client first sends something
> like 9P2000[.extension] and the server responds with something like
> 9Pnnnn. so if we add the extension to like kfs or cwfs, we can
> respond with 9P2010 or something and the mnt driver will use the
> Tmove rpc.
>
> but looking at the implementations... we are in trouble...
>
> cwfs:
>        /*
>         * Should check the '.' stuff here.
>         */
>        if(strcmp(f->version, VERSION9P) == 0){
>                r->version = VERSION9P;
>                chan->protocol = serve9p2;
>                chan->msize = r->msize;
>        } else
>                r->version = "unknown";
>
> lib9p:
>        respond(...):
>                switch(r->ifcall.type){
>                default:
>                        assert(0);
>
> so, just using "P92000" and send blind Tmoves to lib9p based
> server will crash them...
>
> using anything other than "9P2000" will most likely result in
> the Tversion to fail with old servers.
>
> so uriel has a point here...  negotiation my ass...  but this attach
> name hack sucks big time...
>
> --
> cinap
>
>
> ---------- Forwarded message ----------
> From: Uriel <uriel@berlinblue.org>
> To: 9front@googlegroups.com
> Date: Fri, 1 Apr 2011 02:30:02 -0700
> Subject: Re: todo
> On Fri, Apr 1, 2011 at 12:13 AM,  <cinap_lenrek@gmx.de> wrote:
>> why?  can't we just fire and forget?  server that dont know the
>> command will just reply with an error no?
>
> We could just as well 9p2010 and be done with it.
>
> Changing the protocol for this is just stupid, next you will find a
> trillion equally good reasons to add other extensions.
>
> uriel
>
>> --
>> cinap
>>
>>
>> ---------- Forwarded message ----------
>> From: Uriel <uriel@berlinblue.org>
>> To: 9front@googlegroups.com
>> Date: Fri, 1 Apr 2011 00:04:18 -0700
>> Subject: Re: todo
>> On Thu, Mar 31, 2011 at 9:40 PM, aiju <aiju@phicode.de> wrote:
>>>
>>>> This is plain gratuitous idiotic protocol breaking, you can do the
>>>> same thing simply by providing an alternative attach name with ctl
>>>> file(s) for fancy things like moving stuff around.
>>>
>>> It doesn't break the protocol at all: Clients which don't need it
>>> don't have to know about it and if the server doesn't have it the
>>> client can emulate it.
>>
>> But then the client has to negotiate with the server to find out if it
>> supports the Tmove extension,
>> it is totally idiotic and retarded, adding it via an alternative
>> attach name is trivial and doesn't break any shit.
>>
>> uriel
>>
>

  reply	other threads:[~2011-04-01 10:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <405d44d0ddf24c71ff94c72804f03bec@gmx.de>
2011-03-30 20:57 ` todo Stanley Lieber
2011-03-30 22:39   ` todo cinap_lenrek
2011-03-30 22:46     ` todo Stanley Lieber
2011-03-30 22:04 ` todo uriel
2011-04-01  0:30 ` todo Ethan Grammatikidis
2011-04-01  0:47   ` todo Jacob Todd
2011-04-01  0:59   ` todo Uriel
2011-04-01  1:12     ` todo Ethan Grammatikidis
2011-04-01  4:40     ` todo aiju
2011-04-01  7:04       ` todo Uriel
2011-04-01  7:13         ` todo cinap_lenrek
2011-04-01  9:30           ` todo Uriel
2011-04-01 10:18             ` todo cinap_lenrek
2011-04-01 10:24               ` Uriel [this message]
2011-04-01 11:38                 ` todo cinap_lenrek
2011-04-01 13:36                   ` todo Ethan Grammatikidis
2011-04-01 13:54                     ` todo Julius Schmidt
2011-04-01 17:41                       ` todo Uriel
2011-04-01 19:02                         ` todo Ethan Grammatikidis
2011-04-02 14:22                         ` todo aiju
2011-04-02 14:52                           ` todo Ethan Grammatikidis
2011-04-01 17:38                     ` todo Uriel
2011-04-01  7:09     ` todo cinap_lenrek
2011-04-01  6:14   ` todo Taru Karttunen
2011-05-02  7:30 TODO Uriel
2011-05-02 13:25 ` TODO Julius Schmidt
2011-05-02 17:03   ` TODO Uriel
2011-05-02 18:24     ` TODO Iruatã Souza
2011-05-02 19:33       ` TODO ron minnich
2011-05-02 13:45 ` TODO Jacob Todd
2018-02-24 19:53 TODO Kurt H Maier

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='AANLkTi=gN9j_BQM3ya0KiP6r-xcHRMgZuNCPde-hGkkc@mail.gmail.com' \
    --to=uriel@berlinblue.org \
    --cc=9front@googlegroups.com \
    /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).