Christian Kaiser wrote: > If the ajax request is the first request to finish, it disposes the > RunData. > This leads to bad behavour of my http request, because this request has > to deal with a disposed RunData.
RunData is a per-request object that is borrowed from a pool at request creation and returned (and recycled) at request completion. A RunData object is not meant to be shared between different requests. If you believe you must do this, you have a serious design problem in your software. Then again, your main screen request and your Ajax request are totally unrelated from Turbine's point of view. They should use two different RunData objects anyway. > Is this a common problem? > Can I prevent from it? No, this should not happen at any time. > Please let me now if I can provide you with additional information. Well, yes. Let's have a look at some code. This problem sounds very strange to me. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
