Re: Problems with "addref" via socket

Torsten Bronger writes:
 > Okay, I tested heavily and found out how it works.  In contradiction
 > to <http://refdb.sourceforge.net/manual/ch23s03.html#id2657099>, the
 > 408 has a trailing result message.  (Although it is sent with a
 > slight delay.)

This is correct. refdbd should print the total number of datasets
after each 408/413 message.

 > Moreover, while the 403 has terminated content, it
 > is always empty.

As far as I can see, the content is always empty if you run the client
command "addref". If you run "checkref" instead, the duplicate report
is inserted here.

 > 
 > By the way, I wonder what the 404 is for.
 > 
 > Are the docs out of sync with the daemon?

Regrettably so. 404 is not used in the addref command at all. It is
used in getref and getbib though.

I'll fix these errors in the svn versions of the docs.

If you keep bumping into protocol problems, it may be helpful to edit
src/connect.c. The functions send_status() and read_status() contain
commented-out printf() calls which may be helpful to see what the
server and the C client do.

regards,
Markus

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

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H