If anyone is using the EHCacheProvider, I would suggest updating.

Elliot Sprehn and I found some bugs and performance tweaks together today
that should fix several things that have been committed to SVN.

Mark

On Mon, Dec 7, 2009 at 10:19 PM, Mark Mandel <[email protected]> wrote:

> About to go to bed - but just committed to SVN a
> AbstractBaseAsyncDiscardProvider - that allows for object discards to be
> fire asynchronously.
>
> This is a big plus for the EHCacheProvider (which uses this), because it
> won't lock down a object load while waiting for a discard to fire, which can
> happen when doing a get() request.
>
> More tomorrow...
>
> Mark
>
>
> On Tue, Dec 1, 2009 at 9:56 AM, Mark Mandel <[email protected]> wrote:
>
>> Just got my own write up done:
>> http://www.compoundtheory.com/?action=displayPost&ID=447
>>
>> Mark
>>
>>
>> On Thu, Nov 26, 2009 at 12:46 PM, Brian G <[email protected]> wrote:
>>
>>>
>>> On Nov 23, 2:38 pm, Mark Mandel <[email protected]> wrote:
>>> > > How would you suggest handling this?  Some kind of generic teardown?
>>> >
>>> > Sounds good to me :D
>>>
>>> Working like this (based on
>>> http://www.mail-archive.com/[email protected]/msg00730.html
>>> ):
>>>
>>> <cffunction name="setUp" returntype="void" access="public">
>>>        <cfscript>
>>>                variables.beanFactory = createObject("component",
>>> "coldspring.beans.DefaultXmlBeanFactory").init();
>>>
>>>  variables.beanFactory.loadBeansFromXmlFile("/setup/coldspring.xml",
>>> true);
>>>
>>>                variables.transferFactory = variables.beanFactory.getBean
>>> ("ormService");
>>>                variables.transferFactory.getTransaction().advise(this,
>>> "^test");
>>>        </cfscript>
>>> </cffunction>
>>>
>>> <cffunction name="tearDown" output="false" access="public"
>>> returntype="any" hint="">
>>>        <!--- shutdown transfer cache --->
>>>        <cfset variables.transferFactory.getTransfer().discardAll() />
>>>        <cfset variables.transferFactory.shutdown() />
>>> </cffunction>
>>>
>>> <cffunction name="testPrepareEventThingy" output="false"
>>> access="public" returntype="void">
>>>        ...
>>>        ...
>>>        ...
>>>
>>>        <cftransaction action="rollback" />
>>> </cffunction>
>>>
>>> The only bummer to this approach is putting the rollback at the bottom
>>> of every single test function.  Is there a way to make the advice run
>>> a function with the rollback automatically when it completes?
>>>
>>> Thanks!
>>>
>>>
>>> Brian
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>>  --
>> E: [email protected]
>> T: http://www.twitter.com/neurotic
>> W: www.compoundtheory.com
>>
>>
>
>
> --
> E: [email protected]
> T: http://www.twitter.com/neurotic
> W: www.compoundtheory.com
>
>


-- 
E: [email protected]
T: http://www.twitter.com/neurotic
W: www.compoundtheory.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

Reply via email to