From: Andrea A. <and...@ge...> - 2012-06-08 12:04:00
|
On Fri, Jun 8, 2012 at 1:40 PM, Juan Marín Otero <jua...@gm...> wrote: >> One final thing that happened to me while writing processes is >> realizing that a process >> will take long, that it cannot be written in a streaming manner for >> some reason, and thus >> really wanting the process to be only run in asynch mode. >> Ideally it would be nice to have the following: >> >> @DescribeProcess(... synch=false, asynch=true) If a process runs fast > > I really like this idea, and had been wondering about it. I'm not sure if > you want synch and asynch, perhaps only keep asynch with a default value of > false? Hmm... this matches what the WPS protocol exposes, there is no way to say a process cannot be run in a synchronous way, one can only say that asynch is supported or not. Yet, the GeoServer WPS is transparently supporting asynch, so it comes at no extra cost for the implementor, and little extra cost for the server. What I really want is a way to deny synchronous execution of processes that take so long it's unreasonable to think a HTTP call can be kept up that long. Long story short, I believe asynch = true and synch = true is a better fit for the general case, and even if we cannot advertise it, I'd like to have the option to throw an exception if a process is called in synch mode when it has synch = false Cheers Andrea -- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 339 8844549 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf |