Re: [Refdb-users] Problems with "addref" via socket
Status: Beta
Brought to you by:
mhoenicka
|
From: Torsten B. <br...@ph...> - 2009-02-15 16:29:29
|
Hallöchen! Torsten Bronger writes: > Trying to use "addref" > (http://refdb.sourceforge.net/manual/ch23s03.html#id2657099) > through a socket, I get a 406 instead of a 403 after having sent > the 402. What does it mean and how does it fit into the protocol? > It isn't documented at all as far as I can see. 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.) Moreover, while the 403 has terminated content, it is always empty. The complete communication in case of adding something twice is: '6\x00\x00\x00\x00' ==> <== '000' <== '210-82-39-61' <== '\x00\x00\x00\x00' '000addref -d biblio -u root -w 104112047125110\x00\x00\x00\x00' ==> <== '000' '000307\x00\x00\x00\x00' ==> <== '000' u'\nTY - JOUR\nAU - Astakhov,O.\nAU - [...]ER - \n' ==> <== '408' <== '406:1:Astakhov2006wa\n408:1\n\x00\x00\x00\x00' '000307\x00\x00\x00\x00' ==> <== '000' u'\nTY - JOUR\nAU - Astakhov,O.\nAU - [...]ER - \n' ==> <== '408' <== '406:2:Astakhov2006xa\n408:2\n\x00\x00\x00\x00' '402' ==> <== '403' <== '\x00\x00\x00\x00' '000' ==> <== '000' <== '999:2 added:0 skipped:0 failed\n\x00\x00\x00\x00' '000' ==> By the way, I wonder what the 404 is for. Are the docs out of sync with the daemon? Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus Jabber ID: tor...@ja... |