If your Domino server is running on a Windows environment, you can use locks (CreateLock, Codelock, Codeunlock, Destroylock) in your LS agents so that you can be sure concurrents agents will not create conflicts or incoherent situations while working on the same data.
Instead of working with several WQS agents, you can chain them ; I use to do that and it works perfectly. Basically, you redirect your user towards an agent in your $$Return field, which, at the end of its process, redirects him towards another agent, etc etc. It relies on HTTP redirections (no crappy javascript redirection), and if you want them to be more flexible, you can even specify the sequence in parameters (query string), just giving an agent the URL it will have to redirect the user to. Just do not forget to add an URL encoding level every step of your sequence.
Ex : /plop.nsf/first?Openagent&redirect=
%2Fplop.nsf%2Fsecond%3FOpenagent%26
redirect%3D%252Fplop.nsf%252Fthird%253FOpenag
ent (3 levels of URL encoding)
Finally, to avoid most of WQO agents, I use, when possible, that technique : {Link}
It's a kind of data caching in the databases structure, so that you do not have to compute anything (no lookup, no WQO, just including subforms containing HTML code) to "build" a page with data coming from several documents/types of documents. Thus it gives great performances, but it makes the maintaining quite difficult and a bit risky.
Hi Jake,
If your Domino server is running on a Windows environment, you can use locks (CreateLock, Codelock, Codeunlock, Destroylock) in your LS agents so that you can be sure concurrents agents will not create conflicts or incoherent situations while working on the same data.
Instead of working with several WQS agents, you can chain them ; I use to do that and it works perfectly. Basically, you redirect your user towards an agent in your $$Return field, which, at the end of its process, redirects him towards another agent, etc etc. It relies on HTTP redirections (no crappy javascript redirection), and if you want them to be more flexible, you can even specify the sequence in parameters (query string), just giving an agent the URL it will have to redirect the user to. Just do not forget to add an URL encoding level every step of your sequence.
Ex : /plop.nsf/first?Openagent&redirect=
%2Fplop.nsf%2Fsecond%3FOpenagent%26
redirect%3D%252Fplop.nsf%252Fthird%253FOpenag
ent (3 levels of URL encoding)
Finally, to avoid most of WQO agents, I use, when possible, that technique : {Link}
It's a kind of data caching in the databases structure, so that you do not have to compute anything (no lookup, no WQO, just including subforms containing HTML code) to "build" a page with data coming from several documents/types of documents. Thus it gives great performances, but it makes the maintaining quite difficult and a bit risky.
Hope it helps,