In most cases I would make it thread-scoped anyways so the same structure applies.
** Martin 2009/6/9 Frank Tegtmeyer <f...@fte.to>: >> Yes, but not all transactions are request-scoped. We have many times >> implemented asynchronous transactions, because the user didn't want to >> wait for the results. > > Can you give a (high level) overview how to handle such a situation > in Wicket? I'm sure clients will demand such functionality someday > from my application. > I would use some kind of batch processing system with API calls to get > the status of the batch request. Or would this be overkill? > > Regards, Frank > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
