[squeak-dev] Transfer of binary data between images
herbertkoenig at gmx.net
Sat Oct 21 19:06:53 UTC 2017
I used JSON with the addition of carrying the class (JSON being
little work after loading the JSON package. (And because I've been doing
some web application where I needed JSON anyway.)
Each class needs on the class side:
^ self new constructFromJson: j
and on the instance side:
(self class allInstVarNames collect: [:ea| ea asSymbol])
j keysAndValuesDo: [:key :value|
self instVarNamed: key put: value]
Simple, stupid and good enough for several of my applications.
This should work across dialects if the destination image has the
required classes in the same shape. The @Classname designator is a
Smalltalk specific extension to JSON. I think it is not good enough to
transfer object trees with cyclic dependencies. Other languages with a
different ideas of how a class is constructed it might need more work.
Am 21.10.2017 um 18:33 schrieb Kjell Godo:
> Is JSON the preferred way to transfer data between different
> Smalltalk platforms?
> like Dolphin S8 visualWorks GnuSmalltalk Smalltalk/X Amber etc?
> i would like a way for all the different things to talk to each other
> why should they all be seperate?
> I am assuming JSON would be best for going between languages like
> Smalltalk - Lisp
> ( it is the easiest to get access to everything has a Package for
> it ).
> Are there any Packages that are designed to link different languages
> like Smalltalk - Racket - CommonLisp - SWIProlog etc?
> i am assuming that sockets + JSON are the easiest quickest way
> or DCom or what was that Linux d-Bus is d-Bus also on Windows?easy?
> is COM also on Linux?does anyone use it?hard to use?
> Dolphin and VisialWork do COM
> is anyone doing this sort of thing?who would just know?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev