- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] finalization

by stepharo

Ben no stress. Now what I would love is an example that we can put in the uFFI chapter :) Stef Le 6/9/16 Ã 17:32, Ben Coman a Ã©crit : > Apologies. What a bogus post! I must have been really tripping.... > > On Tue, Sep 6, 2016 at 9:26 PM, Ben Coman <btc(a)openinworld.com> wrote: >> I thought I was starting to get a grip on how finalization work. I >> made this example... >> >> Object subclass: #MyObject >> instanceVariableNames: '' >> classVariableNames: '' >> package: 'Play' >> >> MyObject>>autoRelease >> ^ self class finalizationRegistry add: self >> >> MyObject>>finalize >> Transcript crShow: 'Finalizing MyObject' >> >> o := MyObject new autoRelease. >> o := nil. >> Smalltalk garbageCollect. ==> 'Finalizing MyObject' >> >> So far so good. Extrapolating... I would *expect* this... >> >> oc := OrderedCollection new. >> 10 timesRepeat: [ oc add: Libclang getClangVersion ]. >> oc removeAll. >> oc := nil. >> Smalltalk garbageCollect. >> >> ...to print 'Finalizing MyObject' ten times, but it does nothing!! >> > Duh! I didn't send autorelease inside the timesRepeat above... > > Duh^2 !! that example didn't even refer to MyObject!!!!! > > Of course fixing those two things to get... > 10 timesRepeat: [ oc add: MyObject new autoRelease. ]. > works perfectly! > >> Such a simple example feeds my naive presumption that the system seems >> broken. So could someone help me interpret this result ? > Sorry for the noise. Pure PIBKAM**. Couldn't see the trees for the forest. > > cheers -ben > > > **problem is between keyboard and mouse. > >

Sept. 6, 2016

Re: [Pharo-dev] Catalog broken

by stepharo

tx esteban! Le 6/9/16 Ã 20:52, Esteban Lorenzano a Ã©crit : > fixed > >> On 06 Sep 2016, at 16:26, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Trying to open the catalog gives an HTTP 500 error with body contents >> >> <html><head><title>NeoJSONMappingNotFound: No mapping found for ConfigurationOfObjectStatistics class in NeoJSONWriter</title></head><body onload="onLoad()"><h1>NeoJSONMappingNotFound: No mapping found for ConfigurationOfObjectStatistics class in NeoJSONWriter</h1><p>Your request could not be completed. An exception occurred.</p><script type="text/javascript">function onLoad(){};</script></body></html> >> >> Norbert >> >> > >

Sept. 6, 2016

Re: [Pharo-dev] Catalog broken

by Esteban Lorenzano

fixed > On 06 Sep 2016, at 16:26, Norbert Hartl <norbert(a)hartl.name> wrote: > > Trying to open the catalog gives an HTTP 500 error with body contents > > <html><head><title>NeoJSONMappingNotFound: No mapping found for ConfigurationOfObjectStatistics class in NeoJSONWriter</title></head><body onload="onLoad()"><h1>NeoJSONMappingNotFound: No mapping found for ConfigurationOfObjectStatistics class in NeoJSONWriter</h1><p>Your request could not be completed. An exception occurred.</p><script type="text/javascript">function onLoad(){};</script></body></html> > > Norbert > >

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Denis Kudriashov

2016-09-06 19:06 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > >> Is that to say that the network holds them strongly? > > I'm curious, why? > Imaging we send object A from server to client as reference. On client object A will be represented by proxy and any message to it will produce remote interaction with object A on server side. Now what will happen if server will collect object A as garbage? Proxy on client will become broken because it will point to unexisting object on server and any message send will produce error. So simple weak arrays approach is not enough to manage distributed objects. Distributed garbage collection is required which is not implemented yet. Of course it is very important feature but for specific applications manual management is usable too. In case of remote debugging everything is cleaned when client disconnects debugger from server.

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Sean P. DeNigris

Denis Kudriashov wrote >> Is that to say that the network holds them strongly? I'm curious, why? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ann-New-Seamless-version-0-9-0-tp4914168p4914408.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Denis Kudriashov

2016-09-06 18:01 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > But it could be problem if you will manage your domain objects be > > transferred as value. > > I don't understand. Does this relate to classes not being loaded in the > system? > Imaging that you have Point with format (x,y) on server and with format (x,y,z) on client. In such case there will be problems while transferring Point instances as copy (by value) between server and client. But by default most of objects are transferred by reference.

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Denis Kudriashov

2016-09-06 18:01 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Is that to say that the network holds them strongly? yes

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Sean P. DeNigris

Denis Kudriashov wrote > But it could be problem if you will manage your domain objects be > transferred as value. I don't understand. Does this relate to classes not being loaded in the system? Denis Kudriashov wrote > During network lifetime unused proxies and references are not collected. > It > can be performed only manually (for example when you close network and it > collected by itself or there is "network destroy" command). Is that to say that the network holds them strongly? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ann-New-Seamless-version-0-9-0-tp4914168p4914393.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 6, 2016

Re: [Pharo-dev] finalization

by Ben Coman

Apologies. What a bogus post! I must have been really tripping.... On Tue, Sep 6, 2016 at 9:26 PM, Ben Coman <btc(a)openinworld.com> wrote: > I thought I was starting to get a grip on how finalization work. I > made this example... > > Object subclass: #MyObject > instanceVariableNames: '' > classVariableNames: '' > package: 'Play' > > MyObject>>autoRelease > ^ self class finalizationRegistry add: self > > MyObject>>finalize > Transcript crShow: 'Finalizing MyObject' > > o := MyObject new autoRelease. > o := nil. > Smalltalk garbageCollect. ==> 'Finalizing MyObject' > > So far so good. Extrapolating... I would *expect* this... > > oc := OrderedCollection new. > 10 timesRepeat: [ oc add: Libclang getClangVersion ]. > oc removeAll. > oc := nil. > Smalltalk garbageCollect. > > ...to print 'Finalizing MyObject' ten times, but it does nothing!! > Duh! I didn't send autorelease inside the timesRepeat above... Duh^2 !! that example didn't even refer to MyObject!!!!! Of course fixing those two things to get... 10 timesRepeat: [ oc add: MyObject new autoRelease. ]. works perfectly! > Such a simple example feeds my naive presumption that the system seems > broken. So could someone help me interpret this result ? Sorry for the noise. Pure PIBKAM**. Couldn't see the trees for the forest. cheers -ben **problem is between keyboard and mouse.

Sept. 6, 2016

Re: [Pharo-dev] [Ann] New Seamless version 0.9.0

by Denis Kudriashov

2016-09-06 16:37 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > Yes, it is new implementation of remote smalltalk. Look at my blog for > > details and docs > > http://dionisiydk.blogspot.fr/2016/07/major-seamless-update.html > > Wow! This is really awesome. I love that you don't have to have the classes > loaded in the image to deal with the proxies. I've been running into a > problem lately that I have many images with overlapping domains that need > to > talk to each other. > But it could be problem if you will manage your domain objects be transferred as value. Different format of objects in such cases will be problem. > It's gotten messy because by default I use > SimplePersistence and it's easy to get into hairy situations where the data > gets unsynced. Could Seamless be appropriate for general inter-image > communication or is there a better alternative? > It is appropriate. But one important feature is absent now. It is distributed garbage collection. During network lifetime unused proxies and references are not collected. It can be performed only manually (for example when you close network and it collected by itself or there is "network destroy" command). Alternative of course is classic http services (Zinc) without any magic.

Sept. 6, 2016