Sorry about jumping in on this so late, just back from vacation and
still ploughing through backlog.
1) 2.0.0.GA will not be out for a while. Planning a long CR run and
coinciding GA with JGroups 2.5, circa early June.
2) When you say separate caches, you would need separate cache
instan
FYI: I'll meet up with Manik and Bela in NE today/tomorrow.
1) 2.0.0.GA will not be out for a while. Planning a long CR run and
coinciding GA with JGroups 2.5, circa early June.
okey; Steve - when do you expect Hibernate 3.3 to go CR/GA ?
2) When you say separate caches, you would need s
Sorry about jumping in on this so late, just back from vacation and
still ploughing through backlog.
1) 2.0.0.GA will not be out for a while. Planning a long CR run and
coinciding GA with JGroups 2.5, circa early June.
Then this is a big problem. I expect 3.3 much sooner than that...
4)
Max Rydahl Andersen wrote:
That means if you want different behavior for the different "types" of
caches you need separate caches. If the JGroups multiplexer is
available, that's not too bad, as the caches can share a channel. If
we think it through well, they can likely share an overall conf
Steve Ebersole wrote:
Re: #4 : what exactly are these differences? Now is the time to
merge it back...
Forgot to attach the diff to my last message. Here it is.
- Brian
---
C:\dev\hibernate\Branch_3_2\Hibernate3\src\org\hibernate\cache\TreeCache.java
Mon Feb 19 17:05:11 2007
+++ C:\de
Max Rydahl Andersen wrote:
So I started breaking out 3.3 as a separate code base on the Hibernate
svn trunk. The first thing done was this org.hibernate.cache.Cache
splitting. So at this point we now have the ability to be completely
free in how we cache entity-data versus collection-data v
But now looking back at #1, I am no longer certain of the conclusions;
and to me the wiki did not make it clear to me what the "long term"
solution was supposed to be (nor really what the "short term" solution
is/was either). Anyone remember the specific conclusions with regards
to this
Manik can better comment on plans for having separate configurations
(e.g. optimistic vs pessimistic, invalidation vs replication) for
different regions of the cache. But, I know it's not a soonish thing.
That means if you want different behavior for the different "types" of
caches you need
Long-term:
In Hibernate - use seperate caches which you have done for 3.3
Not quite true. What I have done so far is to introduce this
possibility. What happens right now is that there is only a single
RegionFactory implementation which simply "bridges" to the old
CacheProviders. Or per
Long-term:
In Hibernate - use seperate caches which you have done for 3.3
Not quite true. What I have done so far is to introduce this
possibility. What happens right now is that there is only a single
RegionFactory implementation which simply "bridges" to the old
CacheProviders. Or perhap
So I started breaking out 3.3 as a separate code base on the Hibernate
svn trunk. The first thing done was this org.hibernate.cache.Cache
splitting. So at this point we now have the ability to be completely
free in how we cache entity-data versus collection-data versus
query-data versus
Oh, just saw 2.0 is still in BETA... How close are y'all to GA?
Steve Ebersole wrote:
So I started breaking out 3.3 as a separate code base on the Hibernate
svn trunk. The first thing done was this org.hibernate.cache.Cache
splitting. So at this point we now have the ability to be completely
So I started breaking out 3.3 as a separate code base on the Hibernate
svn trunk. The first thing done was this org.hibernate.cache.Cache
splitting. So at this point we now have the ability to be completely
free in how we cache entity-data versus collection-data versus
query-data versus times
2 Notes on putForExternalRead() functionality, in addition to the
solution presented on the wiki:
- PFER only goes through if node does not exist; no-op otherwise
(which is done to avoid the situation of hibernate putting a just read
object into cache and another thread/node have updated i
Ok, so my notes from the call, based on issues from the wiki
1. Multiple caches will probably only formally make it in the next
major Hibernate release - 3.3.
2 Notes on putForExternalRead() functionality, in addition to the
solution presented on the wiki:
- PFER only goes through if nod
OK, Monday 9/26 at 10:00 AM EST it is. Details below. Manik, you had a
problem today joining a conf Ram set up using the # below; you guys
overseas might test it during your Monday and if there's an issue send
me a note by 9:30 EST or so.
Main things to discuss are on
http://wiki.jboss.org/
+1
On 22 Feb 2007, at 18:19, Steve Ebersole wrote:
Brian Stansberry wrote:
Sent this out a while back, but the conf call didn't come off due
to scheduling issues. Time to try again.
How does next Monday, Feb 26 at 10:00 AM EST sound? Once we have
an agreed time I'll send out conference
Brian Stansberry wrote:
Sent this out a while back, but the conf call didn't come off due to
scheduling issues. Time to try again.
How does next Monday, Feb 26 at 10:00 AM EST sound? Once we have an
agreed time I'll send out conference call details. Those cc'ed on the
mailing lists are wel
18 matches
Mail list logo
