Stephen, Out of curiosity, are both applications being initialized with the same transfer.xml and use the same definitions path? If so, then targeting the server scope for cache is the way to go. The only caveat is that your application init code will then have to clear the cache out of server scope to ensure a clean init.
Cheers, Paul On Fri, Nov 28, 2008 at 9:27 AM, Stephen Moretti <[EMAIL PROTECTED]>wrote: > > > 2008/11/28 Bob Silverberg <[EMAIL PROTECTED]> > >> >> Or you could keep the transfer instances as is, and specify SERVER as >> the caching scope for each. Another way of accomplishing the same >> thing as suggested by Chris. I'm not sure what the trade-offs would >> be between those two approaches. >> > > Yeah - I was kinda trying to avoid using the server scope. I've never been > terribly happy with sticking stuff in the server scope, but perhaps this is > the way to go with this. > > Thanks guys. > > Stephen > > > > > -- Paul Marcotte Fancy Bread - in the heart or in the head? http://www.fancybread.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
