Phil, I just posted a new diagram that starts to show the 8th and 9th
layers. The specs for events, producers and consumers, bound to named
type-structure definitions ("types"), are stored at the meta and injects
apps (7) into cloud execution container (8) and into type decoders in
layer 5. Hopefully this helps you see what I was saying.
https://github.com/RabbitPhoneWarrenNetwork/Porcini/wiki/SecureSession
robert
On 12/16/2015 05:22 PM, [email protected] wrote:
Can you make a more detailed vision (with a picture) about this?
As I have a cluster running and am paid to do some stuff with all you
list, I can use some time exploring those avenues.
Phil
On Wed, Dec 16, 2015 at 7:07 PM, Robert Withers
<[email protected] <mailto:[email protected]>> wrote:
Excuse me:
With interfaces I think groovy.
With object serialization I think avro.
With header encoding I think ASN1DER with dynamic extension, we need
variable encoding of statistical objects.
With packages I think gradle.
this would be powerful,
robert
On 12/16/2015 01:00 PM, Robert Withers wrote:
I'd like to add that this is a real challenge to existing players in
BigData, all of who offer solutions in this exact space. Whoever
controls it's specification, controls it's cloud market.
My back of the envelope proposal (my apologies for my
abrasiveness with
this approach) is such:
We develop a dynamic cloud meta & control solution: replicated,
eventually consistent and so on. We define the serialization,
interfaces
and package identification to this meta as open-source standards.
With interfaces I think Avro.
With serialization I think ASN1DER encoding, plus non-fixed dynamic
structure extension.
With package identification I think Gradle. Do we have a groovy
compiler?
I thought I would round out my thinking as I believe this to be an
important opportunity. Given that the new internet is going to be
governed by always running, maximally interactive execution
sites, it
will naturally move to Smalltalk, so I do not think there is
anything
for anyone to be concerned about.
Patience and not reacting emotionally to misinformation in the
marketplace will show true colors. Business is warfare. We have the
advantage.
peace,
robert
On 12/16/2015 12:38 PM, Robert Withers wrote:
Allow me to speak a little on my ideas of a distributed meta
layer and
control layer in cloud deployments with Squeak/Pharo,
hopefully in
bounds.
A distributed system must have an metadata repsoitory
describing the
traffic and activity. If you look at deployment, code that
works with
a type and version of data must be present. With packaging
and dynamic
loading, chunks of code registered to a data type/version in
the meta
demand loads a achunk to do directed work in a particular
deployed
image. BigData event flows and data analysis like to get
replicated
and relocated, in realtime. Supporting this in the meta
definitional
layer and the 1/2 control layer starts to do dynamic,
late-binding in
the network. This is the advantage Squeak/Pharo image-based
environments bring to the business table.
Thank you and apologies,
robert
On 12/16/2015 09:57 AM, H. Hirzel wrote:
Is there a Pharo implementation?
https://avro.apache.org/docs/1.2.0/
On 12/16/15, Robert Withers <[email protected]
<mailto:[email protected]>> wrote:
Please consider Avro.
robert
On 12/16/2015 08:58 AM, H. Hirzel wrote:
If you want to move data to Java then you
probably go for JSON or a
particuar XML format.
On 12/16/15, H. Hirzel <[email protected]
<mailto:[email protected]>> wrote:
No, it is a Smalltalk format.
On 12/16/15, Denis Kudriashov
<[email protected]
<mailto:[email protected]>> wrote:
2015-12-16 14:41 GMT+01:00 H. Hirzel
<[email protected]
<mailto:[email protected]>>:
It probably should be noted here as
well that
http://pharo.gemtalksystems.com/book/PharoTools/SIXX/
Just to know does java implementation
exists?
--
. .. .. ^,^ best, robert
--
. .. .. ^,^ best, robert
--
. .. .. ^,^ best, robert
