On Sat 26-Jun-2010 at 09:38 -0700, Ander wrote:
But it has to be a web-app... Finally I'm using the libhuginbase.so created during the installation as it seems it contains all the function I may need. My goal is simply to replace the qt interface by a web site. I don't think there will be a lot of people stitching big project at the same time (it's more like a few people stitching panorama from any place in the world), so I don't really see big problems of memory management ahead of me. Concerning image handling I don't see what you're talking about, could you tell me more ? Also I don't know a lot of libraries to do what hugin do, but I'm not a specialist.
I'd be concerned about security if you are letting untrusted users use this application: it is easy to trick Hugin to use huge amounts of memory and CPU, Hugin also assumes trusted data, e.g. I have a JPEG file that will make Hugin segfault anytime.
The HTTP model is not well suited to long running processes. I can imagine creating a separate daemon that managed stitching and any preview rendering, but the web-appplication itself would merely be a controller for this.
-- Bruno -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
