Re: About the AV and L1 fields

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.

First, a bug prevented public links to be added to the returned string
if pubinfo does not contain anything else but link elements. That is,
the data were correctly added to the database and correctly retrieved,
but they were simply not added to the result string.

Second, a SQL query bug requested both public and private links when
retrieving the libinfo link elements.

This is now fixed in svn. 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.

regards,
Markus

-- 
Markus Hoenicka
[email protected]
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

------------------------------------------------------------------------------
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