|
Boy are we all in trouble!
Half asleep I went through Appendix A and what I
have found is appalling. Simple mistakes that OpenSRS's developers have
made that are unacceptable and if they can't get it right how do they expect us
to get it. I would like to go on the record as saying this is a very bad
idea. Hopefully I am wrong.... Here are my preliminary
comments:
Page 97 has Two errors:
<!DOCTYPE
OPS_envelope SYSTEM "ops.dtd"> <OPS_envelope> <header>
<version>1.0</version>
<msg_id>112.12121493</msg_id>
<msg_type>standard</msg_type> </header> Next block of code:
<dt_assoc>
<dt_assoc>
<item key="owner">
<dt_assoc>
<item key="first_name">Tom</item>
<item key="last_name">Jones</item>
</dt_assoc>
</item>
<item key="tech">
<dt_assoc>
<item key="first_name">Devil</item>
<item key="last_name">Woman</item>
</dt_assoc>
</item>
</dt_assoc> </item> <--- Ohh here it was from the first piece of code. Looks like someone dropped it here by accident :) THis does not belong!!!! </OPS_envelope> Those are the code errors I have a few more problems that I will post in another message to follow.
|
- Re: Open SRS v2.2 Client Protocol Specification Spetember... Neil H.
- Re: Open SRS v2.2 Client Protocol Specification Spet... Charles Daminato
- Open SRS v2.2 Client Protocol Specification Spetembe... Neil H.
- Re: Open SRS v2.2 Client Protocol Specification ... Charles Daminato
- Re: Open SRS v2.2 Client Protocol Specification ... Daniel Manley
