[ refdb-Bugs-2644739 ] refdbd yields invalid XML as RISX

Bugs item #2644739, was opened at 2009-02-27 10:35
Message generated for change (Comment added) made by bronger
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2644739&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Torsten Bronger (bronger)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdbd yields invalid XML as RISX

Initial Comment:
Using "getref" with refdb using the RISX format, the output is not valid XML because the <entry> end tags are missing the closing angle bracket:

...
    <libinfo user="chantal">
      <notes>accepted for publication</notes>
      <reprint status="NOTINFILE"/>
    </libinfo>
  </entry
</ris>


----------------------------------------------------------------------

>Comment By: Torsten Bronger (bronger)
Date: 2009-02-28 14:26

Message:
I sniffed the socket communication with Wireshark and compared my client
with refdbc.  The difference is that I pass "-E utf-8" and refdbc passes
"-E utf8".  This is then embedded into the XML declaration of the response,
so my response becomes one byte too long.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2009-02-27 11:06

Message:
I've found no trace of this problem in the svn logs of backend-risx.c. I
cannot reproduce it with refdbc, as you've noticed yourself. I'll test this
with the Perl module tonight. However, as refdbc does not add anything to
the data sent by refdbd, I'd rather suspect a bug in your implementation of
the protocol, or a bug in the documentation of the protocol. Looks like a
typical off-by-one error. If nothing else helps, I might try to read your
code (although I'm not familiar with that language you're using) and see if
something jumps at me.

----------------------------------------------------------------------

Comment By: Torsten Bronger (bronger)
Date: 2009-02-27 10:43

Message:
Clarification: It happens if you connect though a socket to refdbd but not
with refdbc.  Each entry is sent as one socket chunk, however, the four
NULLs at the end are one character too early:

"...</libinfo>\n  </entry\x00\x00\x00\x00"


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2644739&group_id=26091

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