Mailinglist Archive: yast-devel (246 mails)

< Previous Next >
Re: [yast-devel] Webyast session with consultant
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Tue, 25 Aug 2009 15:36:07 +0200
  • Message-id: <20090825133607.GA26712@xxxxxxxxxxxxx>
* Josef Reidinger <jreidinger@xxxxxxx> [Aug 25. 2009 15:25]:
I bring notes from today's session with consultant.

Thanks. These notes are quite interesting and helpful !

Second what he think is that we should use route
for each plugin as each plugin should define its routes which it provides.

We deliberately decided against this approach in order to make service
plugins really 'pluggable'. A service plugin just defines an interface
and the client side request this interface. All routing is then
completely transparent.

for a discussion of this topic.

For REST we should look how is designed cloudkit ( and

Hmm, at first sight this seems to conflict with ActiveResource. It
probably needs a closer look though ;-)

Rest tutorial is at
and has some more links on this topic.

We also talk about our webclient and what we should improve. We should
have webclient also rest. Especially we should operate easy on hosts.
Karel propose have sub-resources. So url should look like
/hosts/1/systemtime for setting systemtime on first host.

Agreed, but its simply out of scope for the first deliverable.

Also we give another hints how to change our dynamic creating
ActiveResource to normal classes and have in each plugin usual model,
which should contain a lot of functionality and can be easily tested.
(So we should have something like YaSTController as ancestor and
YaSTResource as model ancestor).

This is tempting but I wonder which of our current problems is solved
by this ?!

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 >
Follow Ups