>>>> As an aside, this need is related to generating direct action URLs without >>>> a context or request (i.e. within a background thread.) Is it worthwhile >>>> to anyone beside me to have a directActionURLForActionNamed(...) method >>>> that doesn't depend on (ERX)WOContext? I keep running into this with >>>> threaded email generation, user-agent headers in a crawler, etc. When I >>>> get some time I may jump on it. >>> >>> It should be easy to assemble: >>> "http://"; + WOHost property + WOCGIAdaptorUrl property + WOApplicationName >>> property + ".woa/" + application.directActionRequestHandlerKey() + "/" + >>> actionName >> this has limitations ... if you have multiple incoming domains, you won't >> know at the time you generate this which domain you should hand back for a >> given user whereas the context would have the domain name they used to come >> into the site. this may or may not be a problem for you. > If he does not have a context or request, falling back to these defaults is > all he can do. Or am I missing something? if you have to do this, you have to do it -- just pointing out that you may run into issues that you need to resolve through some other business logic (i.e. storing most recent accessed domains on the user, etc, so that you can pull it back out when you send emails with urls in them, etc).
ms _______________________________________________ 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]
