On 26-Jul-06, at 11:11 PM, Deepak Nulu wrote:
Hi,The first part of David LeBer's articles on Direct Actions (http:// david.codeferous.com/?p=63) says the following about component actions:"each visitor will receive a relatively heavyweight Session object, so they may not be appropriate if you expect a lot of visitors and/or you do not need to track their state. Direct Action are designed for these situtations."So if I have a direct action which (1) requires a session object, and (2) returns a WOComponent object, will it be as heavy weight as a component action? If not, what is it that makes component actions relatively heavyweight?If I have a site where multiple things can be accessed via direct actions, and if I want some of these things to be available only to registered users, would I need a session object for these direct actions?
Deepak,To be clear, DirectActions have two primary differences between ComponentActions:
1. They have static (bookmarkable) URLs. 2. The use of a Session is optional.Sessions are not bad, there are just times when you do not need one, so why incur the expense? If you need to track user state, a Session is an easy way to do that and for most applications that's where it ends.
-- ;david -- David LeBer Codeferous Software 'co-defer-ous' adj. producing or containing code site: http://www.codeferous.com blog: http://david.codeferous.com -- Toronto Area Cocoa / WebObjects developers group: http://www.tacow.org
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
