Mailinglist Archive: yast-devel (163 mails)

< Previous Next >
Re: [yast-devel] Registration Rest Api
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Fri, 18 Sep 2009 11:23:17 +0200
  • Message-id: <20090918092317.GA12716@xxxxxxxxxxxxx>
* J. Daniel Schmidt <jdsn@xxxxxxx> [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.

run registration and return the/a result

post data:


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.


Hmm, the proxy should belong to the network settings.



This also looks awkward (should be <key>value</key>) but thats
probably due to ActiveResource.



<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

Is there a state diagram available showing how requests and answers
relate ?

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)

To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >