rfc: remove "revision specs"

[Jan Hudec]

On Wed, Aug 31, 2005 at 01:58:22 +0300, Nir Soffer wrote:
> 
> On 31 Aug, 2005, at 1:36, Jan Hudec wrote:
> 
> >So *try* it if you don't believe. If you enter URL with fragment in 
> >browser
> >url-bar, the fragment will *not* become part of the request, so the web
> >application does not have a chance to give it another meaning than 
> >scrolling
> >to an <a name="fragment"> tag. That's how fragments are defined in the 
> >rfc
> >and how they are meant to be.
> 
> Thats a good point, it is ignored :)
> 
> Strange that it is ignored when rfc talks about:
> 
> 	The identified secondary resource may be some
>       portion or subset of the primary resource, some view on 
> representations of
>       the primary resource, or some other resource defined or described 
> by those
>       representations.
> 
> Both last options are not possible when the fragment is not sent to the 
> server.

Make sure to notice, that web browsers are dealing with particular scheme
-- http -- which could make particular choices, in this case the first
option. And since bzr is likely to use http or bzr+http scheme (and bzr+ssh
and such), it has to stick with that choice.

--
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050831/ad576929/attachment.pgp