Filip Hanik - Dev Lists wrote:
This byte based solution doesn't seem useful to me: for example in
JBoss there is support for finer grain replication, and it doesn't use
byte arrays.
I don't think data transfers get more fine grained than a single byte :)
Of course, but using byte[] as a type anywhere is bad, I think (not
recyclable, needs byte copying, etc). Using an indirection like
ByteBuffer or ByteChunk is the minimum.
(don't think you can write a bit to a stream)
If you think of AOP and just transfer data diffs, they still get
transferred as bytes. using byte[] arrays lets the container control the
serialization. this way, you can have as fine or coarse grained as you
want. The API shouldn't impose what serialization mechanism is being
used, that is why it is byte[]
Yes, I was thinking AOP or similar mechanism. Of course, at some point,
it will get to bytes to be transferred to another node, but it's a
feature and format of the transport since the StandardSession will have
no idea how to apply it. If (as I understand it) it's just a callback
which is meant to be implemented by classes which extend
StandardSession, then IMO it is too strict to impose dirty/diff logic. I
still prefer using classes which extend StandardSession and StandardManager.
I'd like to have more explanation why this new APIs are a great idea,
and how they will be used.
of course, very large size clusters, with linear increase in network
chatter, not exponential like today.
more to come...
I have trouble seeing the relation between the proposed API additions to
org.apache.catalina.Session and the capability of having a large cluster ;)
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
