Mailinglist Archive: yast-devel (246 mails)
| < Previous | Next > |
[yast-devel] WebYaST: Vendor service - Summary + TODO
- From: Ladislav Slezak <lslezak@xxxxxxx>
- Date: Fri, 21 Aug 2009 11:47:15 +0200
- Message-id: <4A8E6D23.6060607@xxxxxxx>
(Resending to yast-devel for a broader discussion....)
Dne 21.8.2009 10:08, Jiří Suchomel napsal(a):
I'd reuse the existing right, no need for extra one IMHO.
The question is if vendors would like to change "Custom Services" to a better
name
(with real service name). With current implementation they need to change the
name
directly in .yml config file. Is that OK?
Maybe one AJAX call for all services could be better (I'm not sure about the
overhead, running 30 requests in parallel instead of big one might be too slow.)
Any idea? I'm not an AJAX expert...
I'd keep the same functionality, this creates unnecessary complexity. More over
reading the current status might take long time so the complete page would be
displayed after a (possibly long) delay.
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
Dne 21.8.2009 10:08, Jiří Suchomel napsal(a):
On Thursday 20 of August 2009 13:30:12 Ladislav Slezak wrote:
The REST service
================
- provides a REST API for both LSB and custom services
- uses YaPI for LSB services
- custom services are handled directly, config files are read/parsed
directly, SCR service is used for execution
- uses new YaST::ConfigFile library
Web UI (webclient)
==================
- provides a separate view on LSB services and custom services
- allows custom branding (via modifications in /public directory)
TODO
The REST service
================
- enhance testsuite
- add function to query service status (Q: use new policy for query, or use
the one for "execute"?)
I'd reuse the existing right, no need for extra one IMHO.
Web UI (webclient)
==================
- testsuite
- design the UI (talk to mschmidkunz), may be different for System vs. Custom
services
The question is if vendors would like to change "Custom Services" to a better
name
(with real service name). With current implementation they need to change the
name
directly in .yml config file. Is that OK?
- show the service status:
- for system services, probably first show list of services, that update
the
status of each one service with AJAX calls
Maybe one AJAX call for all services could be better (I'm not sure about the
overhead, running 30 requests in parallel instead of big one might be too slow.)
Any idea? I'm not an AJAX expert...
- custom service is expected to be only one currently, so the status could
be load on loading index page
I'd keep the same functionality, this creates unnecessary complexity. More over
reading the current status might take long time so the complete page would be
displayed after a (possibly long) delay.
- think how the service execution result should be shown better
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
| < Previous | Next > |