Michal Marek wrote:
Adrian Schröter wrote:
On Wednesday 18 June 2008 16:24:35 Michal Marek wrote: ..
Problem #2 (practical): To implement good heuristics, the wizard at least needs to look into the source tarball (if not run some commands...). Here comes the problem: 'tar tf foo-1.1.tar.bz2' can take a *lot* of cpu time, so where to perform such expensive actions? ... What is with having an own service for this but handle it via the API ? We could run this service inside of a chroot or maybe even on a remote system, but not necessary on the backend server. This service would work on the scanning jobs sequential to avoid the DoS. You would need to implement some kind of waiting procedure in the frontend for this to give the user feedback
Sounds like a good idea - implement the wizard in the API, but have a separate service (behind the API) to extract tarballs etc. What do the others think? From an administrative POV - is it possible to get a (virtual) machine for this? (I know you guys are currently busy with the storage problems...)
You could consult your implementation with Andrei Oprisan. He is working on an more intelligent wizard on his Google SoC project: http://www.apkg.org/ He would be happy, if the service API would be compatible with his future APKG frontend API. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org