* J. Daniel Schmidt <[email protected]> [Sep 17. 2009 22:14]:
>
> Run Registration:
> ---------------------------------
>
> * /registration
As Josef already mentioned, you might want to rename this to
/registration/register. This way the url names the action ('register')
and also matches Rails controller/action pattern for urls.
>
> POST
> run registration and return the/a result
>
> post data:
>
> <registration>
> <options>
> <debug>2</debug>
> <nooptional>1</nooptional>
> <nohwdata>1</nohwdata>
This negation seems awkward. What's wrong with <optional> and <hwdata> ?
Boolean attributes should also get boolean values (i.e. 'true' instead
of '1').
But such details (type of attributes) are better left to ActiveResource.
> <forcereg>0</forcereg>
> <httpproxy>http://my.proxy</httpproxy>
> <httpsproxy>http://my.proxy</httpsproxy>
Hmm, the proxy should belong to the network settings.
> </options>
>
> <arguments>
> <argument>
> <name>key</name>
> <value>val</value>
> </argument>
This also looks awkward (should be <key>value</key>) but thats
probably due to ActiveResource.
> ...
> </arguments>
> <registration>
>
>
> returns:
>
> <registration>
> <status>finished|missinginfo|error</status>
> <message>Some text to display</message>
Where does this message come from, how is it translated ?
Language setting should be a property of the frontend (webclient), the
service has no idea about the UI language.
For the error results, use different class definitions all derived from a
common 'error' class. I guess discussing these classes is easier than
looking at raw xml.
>
>
> There is only one action to perform the registration. And all data has to be
> send for each request, as it operates in stateless context.
> The following action depends on the answer to the request. If there are
> arguments missing a following call is needed (together with the additional
> arguments).
Is there a state diagram available showing how requests and answers
relate ?
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
