On Wed, 13 Feb 2002, Scott Allan wrote: > - I would note that many people have been able to get things working on > different platforms
This seems to be a popular response to my quibble. Multiple people have pointed out to me that it's work with different languages/platforms. I know, I am one of those people! The point is that there is a significant barrier to those wishing to write a client using a different language who do not already know perl because the protocol docs are so poor. I don't think it's an appropriate solution to say go look at the PHP client, or this and that client (what if I don't know those languages?). However, that's the only answer today. I took the time to learn an adequate amount of perl so I could understand OpenSRS's implementation. And after dealing with perl's black magic, I much rather would have had plain ol' protocol docs. The protocol is actually quite simple, but is made out to be a bear. > - if you are not getting responses to your questions, we can correct this - > just drop us a note off-list with your ticket numbers and we can follow > through - protocol questions can be trickier as they are not as common, so > our response time is likely slower - posting protocol questions to this > list can be a quick way to get the info you seek, as many here have worked > it out already, or are "in the know" The only outstanding question I have now is whether or not OpenSRS is going to provide a current DTD for the protocol. I'm not quite sure when it was available or when it disappeared, but it certainly hasn't been included in any of the 2.4x releases. I have no problem keeping my own DTD up to date. But the issue becomes more difficult should there ever be a significant change and is not properly documented. I will be more than happy to follow this up off-list if it can't be answered here. -- Robert Dale digital mission llc
