Subject Re: Strategic Replacement for Services API
Author Roman Rokytskyy
> That strikes me as particulary awkward. How about something like:
>
> <Request operation="createDirectory">
> <Directory
> path="/var/www/html/demo"
> name="demo"
> index="home.nfs"
> webSite="DefaultSite"
> documentRoot="/var/www/html"
> createDocument="home.nfs"
> parentPath="/var/www/html">
> <Handler
> extension=".nfs"/>
> <Application
> database="MANCHESTER@localhost"
> application="mbts"
> account="admin"
> password="xxxxxx"/>
> </Directory>
> </Request>
>
> A little face value goes a long way.

Requires creating a parser for each new call. So, with the same effect
you could do

POST /FirebirdService HTTP/1.0
User-Agent: Frontier/5.1.2 (WinNT)
Host: betty.userland.com
Content-Type: text/plain
Content-length: 181

directory.path=/var/www/html/demo
directory.name=demo
directory.index=home.nfs
directory.webSite=DefaultSite
directory.documentRoot=/var/www/html
directory.createDocument=home.nfs
directory.parentPath=/var/www/html
handler.extension=.nfs
application.database=MANCHESTER@localhost
application.application=mbts
application.account=admin
application.password=xxxxxx

This one at least is easier to handle. The XML there is of no use.

Roman