> I'd go with a java resource-style before I'd go with this, it looks heavy
> and lacks legibility despite the indentation. The layout doesn't matter so
> we could do without XML for backends.
Forget about the legibility (your parser will solve that), and,
yes it is "heavy", but it is also extremely portable, extensible
and easy to follow.
The *trick* (in my opinion of course), is to make the client-server
communication API simple to understand and based on open standards.
That way, if I want to write a client in Perl, PHP, C, Java ...
or Japanese, I only have to interface my language of choice to an
open standard, not necessarily to another language.
Like I said, it was just a suggestion. I would be curious as to
what the OpenSRS Dev Team thinks.
__________________________________________________________________
Colin Viebrock easyDNS Technologies
Co-Founder control your domain
http://www.easyDNS.com
