We've never made delegates singletons - since typically these are
reusable proxies to server-side business logic, and there has never been
a need to have the "same instance of the singleton" between different
command invocations.
Doesn't mean making a delegate a singleton is wrong; it's
application-specific I guess, and it's a freedom you have as a developer
using Cairngorm, to make these decisions.
Best,
Steven
Steven Webster
Practice Director (Rich Internet Applications)
Adobe Consulting
Westpoint, 4 Redheughs Rigg, South Gyle, Edinburgh, EH12 9DQ, UK
p: +44 (0) 131 338 6108
m: +44 (0) 7917 428 947
[EMAIL PROTECTED]
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tim Hoff
> Sent: 17 April 2006 19:08
> To: [email protected]
> Subject: [flexcoders] Re: Cairngorm2 Commands and Singletons
>
> Making the delegate a singleton solved the problem. Thank
> you very much for the insight.
>
> - TH
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
