RE: cvs commit: cocoon-2.1/src/blocks/eventcache/java/org/apache/ cocoon/caching/impl StoreEventRegistryImpl.java DefaultEventRegistryImpl. java

["Hunsberger, Peter" <Pe...@stjude.org>]

Geoff Howard <co...@leverageweb.com> WRITES:

<snip/>

> >Two questions.
> >1. Is eventcache stable enough for me to use or will it be 
> undergoing 
> >radical changes?
> >  
> 
> That's a good question.  It's still marked alpha/stable/whatever but 
> that is more by inaction than purposeful decision (at least on my 
> part).  Of course it's up to the larger community but it's 
> been mostly 
> Unico and myself that have worked on it.  Practically, I'd feel more 
> comfortable having heard from more people who have used it before 
> locking it down - so your use could contribute to its stability. 

We finally have resources scheduled to look at integrating our code with
your code, the time frame is currently mid-summer, so don't hold your
breath...
 
> Having said that, it's a simple API and shouldn't need much 
> tweaking.  
> In fact, the part of the API you would rely on is two _very_ simple 
> interfaces (Event and EventAware).  The only thing I ever imagined 
> affecting that is a feature I envisioned originally 
> ("wildcard" events) 
> but which never came to pass.  I have since wondered whether 
> they would 
> be all that useful and now feel they could probably be 
> implemented in a 
> back-compatible way anyway.  Originally I was questioning the 
> use of Map 
> based hash lookup for events because that would (probably) 
> not support 
> wildcards. 
> 
> Maybe we should consider marking the block "stable"?

+1 That would be good from our perspective.  If it made it into 2.1.6 as
stable we'd be more comfortable depending on it.

> 
> >2. From the vague description I have given does this sound like a 
> >"proper" usage of eventcache?
> >  

<snip/>

Re: cvs commit: cocoon-2.1/src/blocks/eventcache/java/org/apache/ cocoon/caching/impl StoreEventRegistryImpl.java DefaultEventRegistryImpl. java

[Geoff Howard <co...@leverageweb.com>]

Hunsberger, Peter wrote:

>Geoff Howard <co...@leverageweb.com> WRITES:
>
><snip/>
>  
>
>>>Two questions.
>>>1. Is eventcache stable enough for me to use or will it be 
>>>      
>>>
>>undergoing 
>>    
>>
>>>radical changes?
>>> 
>>>      
>>>
>>That's a good question.  It's still marked alpha/stable/whatever but 
>>that is more by inaction than purposeful decision (at least on my 
>>part).  Of course it's up to the larger community but it's 
>>been mostly 
>>Unico and myself that have worked on it.  Practically, I'd feel more 
>>comfortable having heard from more people who have used it before 
>>locking it down - so your use could contribute to its stability. 
>>    
>>
>
>We finally have resources scheduled to look at integrating our code with
>your code, the time frame is currently mid-summer, so don't hold your
>breath...
>  
>

That's good to know - I'll look forward to it.  By the way, mi code es 
su code...

> Having said that, it's a simple API and shouldn't need much 
>tweaking.  
>In fact, the part of the API you would rely on is two _very_ simple 
>interfaces (Event and EventAware).  The only thing I ever imagined 
>affecting that is a feature I envisioned originally 
>("wildcard" events) 
>but which never came to pass.  I have since wondered whether 
>they would 
>be all that useful and now feel they could probably be 
>implemented in a 
>back-compatible way anyway.  Originally I was questioning the 
>use of Map 
>based hash lookup for events because that would (probably) 
>not support 
>wildcards. 
>
>Maybe we should consider marking the block "stable"?
>  
>
>
>+1 That would be good from our perspective.  If it made it into 2.1.6 as
>stable we'd be more comfortable depending on it.
>  
>

:)  Sounds like another chicken and egg.  Murphy's law says that if we 
mark it a stable API and you test it this summer, you'll need the API 
changed...

Ok, I'll start a discussion on the move from alpha.

Geoff