[Seaside] Need help fixing my image
sebastian at flowingconcept.com
Tue Jan 4 12:00:28 UTC 2011
Came on, almost nothing deals with persistence of blocks or closures or compiled methods.
It's not only hard but a whole different problem related to distributed computing (or multi VM computing) with objects which is another beast.
In that field, chances are that:
1. it's going to be your worst idea ever (see Martin Fowler's First Law of Distributed Object Design)
2. you don't need that
3. if you do it, by the time you have it, everything was reinvented in a simpler way (so its usability will scale better and will make you feel miserable)
On Jan 4, 2011, at 8:58 AM, Norbert Hartl wrote:
> On 03.01.2011, at 20:58, Lukas Renggli wrote:
>>>>> Came on, the guy is in a hurry, are you telling that SIXX will not handle his bunch of pages?
>>>> It might work for a bunch of pages, but certainly not something to do
>>>> regularly. Furthermore, you might need to fix the model manually
>>>> before and after the export/import, because SIXX does not handle all
>>>> objects well.
>>> Can you elaborate on this? I'm using Sixx all the time (well, I don't have a choice because there is no ReferenceStream in gemstone). What objects are this?
>> Code, e.g. Blocks and CompiledMethods. Nowadays the Pier model should
>> be free of those (that wasn't always the case) as they don't work well
>> with most persistency mechanisms.
> Ok, you are right. I'm looking again from the cross-platform view. Sixx is changed to support blocks (in gemstone at least). It may not support all kind of blocks but basic ones it does. The rest is like CompiledMethods. AFAIK there is no cross-platform format for things like CompiledMethod so there is less chance to have something reliable. I try to be pragmatic and from this point of view the support is quite sufficient.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside