Comments below.
Niclas Hedhman wrote:
see below
On Sat, Feb 4, 2017 at 6:21 PM, "Michał Kłeczek (XPro Sp. z o. o.)"<
michal.klec...@xpro.biz> wrote:
Once you transfer the code with your data - the issue of code version
synchronization disappears, doesn't it?
It also makes the wire data format irrelevant. At least for "short lived
serialized states".
Only works if you have no exchange with the environment it is executing.
And this is where "sandboxing" concern kicks in. What is the sandbox? In a
web browser they try to define it to DOM + handful of other well-defined
objects. In case of Java Serialization, it is all classes reachable from
the loading classloader. And I think Gregg is trying to argue that if one
is very prudent, one need to manage this well.
But how is "exchange with the environment it is executing"
actually different when installing code on demand from installing it in
advance???
The whole point IMHO is to shift thinking from "moving data" to
"exchange configured software" -
think Java specific Docker on steroids.
Transferable objects allow you for example to do things like
downloading your JDBC driver automagically without the fuss of
installing it and managing upgrades.
Just publish a DataSource object in your ServiceRegistrar and you are done.
Make it leasable and you have automatic upgrades and/or reconfiguration.
Thanks,
Michal
