Re: About the AV and L1 fields

Hallöchen!

Markus Hoenicka writes:

> Torsten Bronger writes:
>
>> Are pubinfo and libinfo inextricably intertwined or perfectly
>> separated?
>
> They are supposed to be treated separately. Your example helped to
> fix two unrelated bugs which caused the behaviour you saw.

Thank you!

> [...]
>
> [...] However, there is one thing to keep in mind. The current
> implementation uses a simple check for "file://" at the start of
> each link to make sure a libinfo link is an URL pointing to a file
> resource owned by the user, and not a public URL accessible via
> http or ftp. That is, libinfo links using any protocol other than
> "file://" or none at all end up being added as public links. This
> code has been added too long ago to exactly remember why it was
> added. It now looks a little strange to me, and I'm open to
> suggestions whether or not to remove this restriction.

In my opinion, it should be removed.  If a private link is turned
into a public one implicitly, this is a source of irritation.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus
                   Jabber ID: [email protected]


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p