![](https://seccdn.libravatar.org/avatar/d18d0fd84170a8255c30388a800b96c8.jpg?s=120&d=mm&r=g)
* Josef Reidinger <jreidinger@suse.cz> [Aug 18. 2009 12:35]:
Yes, it is similar how I implemented it now except, that it remember done steps in backend and not session, so if you configure two modules and another three remain, then you can just after new login configure remaining three.
I fail to see the need for this. Storing such status in the backend either needs an extension to every service or a separate 'workflow status' service.
I hope I have to the end of week working prototype. And then we could discuss about improvements. (I think that practical example shows more problems then theoretical discussion).
Agreed. But even spending half a day on a prototype shouldn't be done without planning and discussing the concept. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org