I use the SERVER scope to store the Windows Scripting Host object, since I use it a lot in my applications at home. So I only ever need to create the object once and store it in the server scope.
�
Are there any disadvantages to this?
As long as you control all of the applications that get deployed on your server, I see no problem with it. macromedia.com uses server scope extensively to share objects between applications (although there's really only one "application" on macromedia.com) - for objects that are expensive to create but are used often.
Sean A Corfield -- http://www.corfield.org/blog/
"Conform! Consume! Obey!" -- Mr Snaffleburger : http://www.matazone.co.uk/theotherside.html
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
