broil, then allow to rest

1 - Hopefully enough other people will read this, and also realize that they don't really 'save' memory or performance by passing a NotesSession object around in their code (because they were afraid to instantiate it elsewhere again).

I've seen lots of code like "DoStuff(mySession)", passing a NotesSession object to the DoStuff() function....not neccessary, it just clutters up the code.

2 - I knew that, but I usually just use a global Session variable because I'm too lazy to redeclare and reinstantiate it. If it's there and Notes knows it's there, why do I have to constantly tell Notes it's there? It would be awesome if Notes had some built in base level of objects that "just knew", like "this" in Javascript, or "Me" in a LS class.

3 - I did know that, but it's a fairly recent piece of knowledge for me, so I too have many routines in the closet which pass around NotesSession objects

If only this sort of stuff was properly documented somewhere eh!

4 - I learned this over the summer at the Advisor Conference in Phoenix. Rocky Oliver was the imparter of this knowledge.

5 - AgentContext in Java agents is similar (and a little more dangerous...)

{ Link }