| Re: [smila-user] SMILA vs Human Computing |
From having a quick look at the ODE source code it does not seem to be possible to set this timeout to “infinity”. But on the other hand, I suppose 2 million seconds will seem very much like “infinity” to a waiting user (-; (Up to SMILA 0.9 the maximum value is Integer.MAX_VALUE milliseconds, because the timeout is stored as an Integer value in our ODE integration. I just changed this to a long variable for SMILA 1.0). Note that you will also have to increase timeouts in configuration/org.eclipse.smila.http.server/jetty.xml, if the browser should wait for a response that long. There is a line like this: <Set name="maxIdleTime">300000</Set> That sets the timeout for an HTTP request to 5 minutes, too. Grüße, Jürgen. From: smila-user-bounces@xxxxxxxxxxx [mailto:smila-user-bounces@xxxxxxxxxxx] On Behalf Of Ilio Catallo Hi Juergen, what you have described is exactly our use case. So it seems that the only feasible way is to extend the timeout parameter. Is it possible to set it to infinity? Ciao, Ilio. Il giorno 09/gen/2012, alle ore 10:09, Jürgen Schumacher ha scritto: I must admit that I have problems understanding your use case (maybe because it’s Monday morning...). In your mail it sounds like this to me: - A user goes to a search page and enters a search. - Then he waits while in the background some processing is done. - At one point this processing waits for confirmations from other users, the “crowd”. - When this confirmation has arrived the search result is shown to the initial user. If that’s correct then you are right, it would not be possible easily to split this in two pipelines, and I don’t see any other solution than to increase the timeout for BPEL pipelines and let a pipelet wait for the confirmation. Anyway, how long would the searching user wait for the confirmation? If that’s not the correct use case, maybe you can explain it again to me (and my colleagues)? Cheers, Juergen. _______________________________________________ |