> If you were using a dispatch action, aren't there decent odds that you'd need > to dispatch cancellations too?
I dunno Joe. DispatchAction is designed so that it can only have one cancel handler; but if it didn't have cancelled(), every action could have the option of doing something different. But point of note: DispatchAction cancelled() is called ON EVERY CANCEL, but if "null" is return, it's considered "not implemented" and proceeds to the original method. That's BAD DESIGN; the contract of the action execute-like method is to return null if the response is handled directly, not to mean it's not implemented. Paul __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
