Serdar Basegmez
Last time, I have blogged about the importance of the importantance of canceling tasklets...
In most of the time, canceling a task is a 'choice' you have. You might want to stop the task for a reason. However, a very important problem is falling into deadlocks. If somehow your code falls into a deadlock or stuck situation, that would lock your DOTS container entirely.
I just wanted to emphasize an important functionality within DOTS...
One of our slides in the recent DOTS session in IBM Connect 2013, we have talked about the "monitor " argument in tasklets. It has two important uses.
After a successful IBM Connect session, I started a series of posts, based on feedbacks I received from other developers.
There was a little thing I didn't test before the session and this issue has been asked a couple of times: Possible conflicts between scheduled tasklets.
I was there, at IBM Connect 2013. My second Orlando visit was far more greater this time. A speaker badge combined to the IBM Champion ribbon, more experience and more fun!
Last year was my first Lotusphere. I had a great pleasure visiting labs and talking to developers from IBM.
I have met to David Taieb and we were discussing about an idea (or a suggestion) about XPages. We are lacking a (distributed) back-end processing system for XPages. When you have to run a really long process in your application which could be a reporting, calculation or so forth, you don't have anything but to keep users waiting with an hour glass.