From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] webfsget
Date: Fri, 14 Jul 2006 22:08:14 -0500 [thread overview]
Message-ID: <3e39e73e871bc0288e096319ef678423@quanstro.net> (raw)
In-Reply-To: <8a4201c1cf1adb577934ad13bddcc2ed@cat-v.org>
i'm not convinced that a web browser needs to merge urls yet.
abaco de-relativeizes urls in a number of places. it would be
better for webfs to do that instead.
anyway, now that webfs does what it claims to do,
i realize the bug i've been tracking has nothing to do with relative urls.
so it's been useful for that. ☺
- erik
On Fri Jul 14 22:11:14 CDT 2006, uriel@cat-v.org wrote:
> I wonder if webfs should handle relative URLs at all. It adds a lot
> of complexity and I can't see any good use for it. I suspect the idea
> was to avoid other apps having to know how to parse and merge URLs,
> but in practice a web browser needs to know how to do that stuff
> anyway.
>
> Did you find a good use for this feature?
prev parent reply other threads:[~2006-07-15 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 0:27 erik quanstrom
2006-07-15 1:58 ` Dan Cross
2006-07-15 1:54 ` erik quanstrom
2006-07-15 3:10 ` uriel
2006-07-15 3:08 ` erik quanstrom [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=3e39e73e871bc0288e096319ef678423@quanstro.net \
--to=quanstro@quanstro.net \
--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).