; use of the horrible old mechanism may still be a worthy goal, even if it
> can't be killed outright.
>
Also many serialization-based libraries use sun.misc.Unsafe or
sun.reflect.ReflectionFactory for various reasons (with backup plans if such
classes are not available or acces
On 12/08/2014 10:03, Peter Firmstone wrote:
Interesting, language features for modules, won't necessarily involve
ClassLoader's (my assumptions were based on existing systems) although
you'd expect modules to have their own ProtectionDomain.
I think it would be reasonable to expect to that y
Interesting, language features for modules, won't necessarily involve
ClassLoader's (my assumptions were based on existing systems) although you'd
expect modules to have their own ProtectionDomain.
An alternative to isolates, is separate processes with jvm class sharing
enabled.
I'll keep an e
On 11/08/2014 13:06, Peter Firmstone wrote:
Thanks Alan, I can relate to time poverty :)
I might be assuming too much, but if there's interest in doing
something with Serialization, I'd be interested in learning about
plans or difficulties involved in deserialization and modules. It can
be a
Thanks Alan, I can relate to time poverty :)
I might be assuming too much, but if there's interest in doing something
with Serialization, I'd be interested in learning about plans or
difficulties involved in deserialization and modules. It can be a
little more difficult to find the correct C
On 09/08/2014 06:56, Peter Firmstone wrote:
I've noticed there's not much interest in improving Serialization on
these lists. This makes me wonder if java Serialization has lost
relevance in recent years with the rise of protocol buffers apache
thrift and other means of data transfer over byt
On 11/08/2014 8:12 PM, Peter Firmstone wrote:
Brian,
Thanks for picking up on my frustration ;)
I have something in mind for Serializable2 to address cyclic data
structures and the possibility of independant evolution of super and
child classes, while retaining a relatively clean public api,
Brian,
Thanks for picking up on my frustration ;)
I have something in mind for Serializable2 to address cyclic data
structures and the possibility of independant evolution of super and
child classes, while retaining a relatively clean public api, with one
optional private method. The methods
I've noticed there's not much interest in improving Serialization on
these lists. This makes me wonder if java Serialization has lost
relevance in recent years with the rise of protocol buffers apache
thrift and other means of data transfer over byte streams.
I sense your frustration, but I thi
I've noticed there's not much interest in improving Serialization on these
lists. This makes me wonder if java Serialization has lost relevance in recent
years with the rise of protocol buffers apache thrift and other means of data
transfer over byte streams.
The burden of implementing Seriali
10 matches
Mail list logo
