November 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3220 in pharo: SystemNavigation: Better System

by pharo＠googlecode.com

Updates: Status: Fixed Labels: Milestone-1.2 Comment #1 on issue 3220 by marcus.denker: SystemNavigation: Better System http://code.google.com/p/pharo/issues/detail?id=3220 (No comment was entered for this change.)

Nov. 9, 2010

Re: [Pharo-project] Installing Glorp in Pharo 1.1

by Giuseppe Luigi Punzi

Ok, I tried again with Yanni instruction, but without '{' '}' and now seems to be installed. Sorry for the noise. El mar, 09-11-2010 a las 16:31 -0300, Mariano Martinez Peck escribiÃ³: > > Worked.. > > > ! > > (ConfigurationOfGlorpDBX project version: '1.2') load: > { 'All with > > PostgreSQL native'. } > > > Failed with: Error: Name not found: All with PostgreSQL native > > But It worked with > > (ConfigurationOfGlorpDBX project version: '1.2') load: > 'default' > > > > But this will install SqueakDBX as the database driver. IF this is > what you want, then it is ok. If you want the postgresql native > driver, you should do: > > (ConfigurationOfGlorpDBX project version: '1.2') load: 'All with > PostgreSQL native' > > should work. > > Otherwise, browse ConfigurationOfGlorpDBX >> baseline12: and see in > the groups definitions if such group is defined. It should. > > Cheers > > Mariano > > > Thanks. > > -- > -- > Giuseppe Luigi > http://www.lordzealon.com > > > -- -- Giuseppe Luigi http://www.lordzealon.com

Nov. 9, 2010

Re: [Pharo-project] Installing Glorp in Pharo 1.1

by Giuseppe Luigi Punzi

Hola Mariano, El mar, 09-11-2010 a las 16:31 -0300, Mariano Martinez Peck escribiÃ³: > > Worked.. > > > ! > > (ConfigurationOfGlorpDBX project version: '1.2') load: > { 'All with > > PostgreSQL native'. } > > > Failed with: Error: Name not found: All with PostgreSQL native > > But It worked with > > (ConfigurationOfGlorpDBX project version: '1.2') load: > 'default' > > > > But this will install SqueakDBX as the database driver. IF this is > what you want, then it is ok. If you want the postgresql native > driver, you should do: > > (ConfigurationOfGlorpDBX project version: '1.2') load: 'All with > PostgreSQL native' This is the content of baseline12: baseline12: spec <version: '1.2-baseline'> spec for: #pharo do: [ spec blessing: #baseline. spec repository: 'http://www.squeaksource.com/SqueakDBX'. spec package: 'Glorp' with: [ spec preLoadDoIt: #loadUnderscoreFix ]. spec package: 'GlorpPostload' with: [ spec requires: #('Glorp') ]. spec package: 'GlorpTest'. spec package: 'GlorpTestPostload' with: [ spec repository: 'http://www.squeaksource.com/Glorp' ]. spec package: 'GlorpPharoPort' with: [ spec repository: 'http://www.squeaksource.com/Glorp'. spec requires: #('GlorpPostload') ]. spec project: 'SqueakDBX' with: [ spec className: 'ConfigurationOfSqueakDBX'; file: 'ConfigurationOfSqueakDBX'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]. spec package: 'GlorpDriverSqueakDBX' with: [ spec postLoadDoIt: #postLoadGlorpDriverSqueakDBX. spec requires: #('SqueakDBX') ] . spec package: 'GlorpDBX-ConnectionPool' with: [ spec postLoadDoIt: #postLoadGlorpDriverSqueakDBXConnectionPool. spec requires: #('GlorpDriverSqueakDBX') ] . spec package: 'PostgresV2' with: [ spec repository: 'http://www.squeaksource.com/PostgresV2' ]. spec package: 'GlorpDriverPostgreSQL' with: [ spec repository: 'http://www.squeaksource.com/PostgresV2'. spec postLoadDoIt: #postLoadGlorpDriverPostgreSQL. spec requires: #('PostgresV2') ]. spec group: 'default' with: #('GlorpSqueakDBX'); group: 'Core' with: #('Glorp' 'GlorpPostload' 'GlorpPharoPort'); group: 'Tests' with: #('GlorpTest' 'GlorpTestPostload'); group: 'GlorpSqueakDBX' with: #('Core' 'Tests' 'GlorpDriverSqueakDBX'); group: 'GlorpSqueakDBX Pool' with: #('GlorpSqueakDBX' 'GlorpDBX-ConnectionPool'); group: 'All with PostgreSQL native' with: #('Core' 'Tests' 'GlorpDriverPostgreSQL'); yourself. ] What I want, is to load the SmallPOS in SqueakSource to try it, and it needs Glorp -- -- Giuseppe Luigi http://www.lordzealon.com

Nov. 9, 2010

Re: [Pharo-project] Process-specific state broken and uncomplete

by Philippe Marschall

On 09.11.2010 07:17, Igor Stasenko wrote: > On 9 November 2010 08:06, Philippe Marschall <kustos(a)gmx.net> wrote: >> On 08.11.2010 06:39, Igor Stasenko wrote: >>> Hello, >>> >>> i just found that Squeak images Process class contains unused ivars: >>> island env >>> >>> in Pharo image, env ivar is used for holding a process-specific state, >>> which is convenient, so one could use: >>> Processor activeProcess environmentAt: put:... >>> >>> but in Squeak image there is even no such methods. >>> >>> There are also some caveats with such thing: >>> during process termination, Processor activeProcess could point to >>> different process, >>> and so, accessing to process environment may lead to error(s). >>> >>> To avoid issues like these, the process termination action (stack >>> unwinding) should be always performed only for active process. >>> One of a trick i think, is to replace the suspendedContext with own >>> context, and then activate given process in order to unwind its stack >>> etc. >>> >>> Another way is to remember environment somewhere else during process >>> termination, and use different method to access it i.e. instead of: >>> Processor activeProcess environmentAt: >>> use >>> self processEnvironmentAt: >>> >>> where #processEnvironmentAt: is implemented in Object class, and can >>> handle termination gracefully. >>> >>> But i think replacing suspendedContext is more generic. >>> What you think? >> >> Not so convinced. Fast thread locals are important and a Symbol lookup >> in an IdentityDictionary is pretty fast. And polluting Object with stuff >> that doesn't belong there isn't a very convincing alternative to me. >> > does that means that you prefer to replace suspendedContext? I prefer to keep env. I can live with the current limitations. Process termination is just so tricky (as other languages found out as well) that it's IMHO better to simply avoid it (like finalization) instead of coming up with some clever hacks to fix it. VW for example has three or four methods to terminate a process. Cheers Philippe

Nov. 9, 2010

Re: [Pharo-project] Installing Glorp in Pharo 1.1

by Mariano Martinez Peck

> Worked.. > > > ! > > (ConfigurationOfGlorpDBX project version: '1.2') load: { 'All with > > PostgreSQL native'. } > > Failed with: Error: Name not found: All with PostgreSQL native > > But It worked with > > (ConfigurationOfGlorpDBX project version: '1.2') load: 'default' > > But this will install SqueakDBX as the database driver. IF this is what you want, then it is ok. If you want the postgresql native driver, you should do: (ConfigurationOfGlorpDBX project version: '1.2') load: 'All with PostgreSQL native' should work. Otherwise, browse ConfigurationOfGlorpDBX >> baseline12: and see in the groups definitions if such group is defined. It should. Cheers Mariano > Thanks. > > -- > -- > Giuseppe Luigi > http://www.lordzealon.com > > >

Nov. 9, 2010

Re: [Pharo-project] Installing Glorp in Pharo 1.1

by Giuseppe Luigi Punzi

Hi Yanni, El mar, 09-11-2010 a las 13:50 -0500, Yanni Chiu escribiÃ³: > On 09/11/10 12:59 PM, glpunzi(a)lordzealon.com wrote: > > Hi all, > > > > I'm trying to install Glorp in Pharo 1.1. I connected to Glorp > > Squeaksource repo, and Loaded the GlorpPharoLoader package. > > Try something like: > > "GlorpDBX" > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfGlorpDBX'; > load. > ! > ConfigurationOfGlorpDBX ensureMetacello. Worked.. > ! > (ConfigurationOfGlorpDBX project version: '1.2') load: { 'All with > PostgreSQL native'. } Failed with: Error: Name not found: All with PostgreSQL native But It worked with (ConfigurationOfGlorpDBX project version: '1.2') load: 'default' Thanks. -- -- Giuseppe Luigi http://www.lordzealon.com

Nov. 9, 2010

Re: [Pharo-project] #& in Socket >> #waitForSendDoneFor:

by Philippe Marschall

On 09.11.2010 07:58, Schwab,Wilhelm K wrote: > What does your patch do? It replaces the #& with and #and: swaps receiver and argument to preserve the same semantics. That saves a primitive call if the data is already sent. It's basically the same as posted by Levente. > At a minimum, it deserves a little attention. Things that come to mind are that one version does less work due to some type of optimization (and runs faster as a result) or that one is too quick to detect a loss of connection and sends less data per opportunity, appearing to run slower as a result. > > Can you elaborate on "I'm able to push about 1 Mbyte/s more"? I guess I'm asking how that manifests itself? Are there a bunch of connections that form, send and fail? Do they each get a little farther or do they go faster? Throughput outgoing from the Pharo image was about 1 Mbyte/s higher. Now I can't reproduce it anymore so it was probably a measuring inaccuracy. That was making 100000 HTTP requests with Apache bench, keep alive and a concurrency level of 10. Apache (the server, not the bench) opens 10 persistent worker connections to the Pharo image each having it's own process an socket so the load should be pretty well spread across them. Then it's Seaside and writing a constant 16 Kbyte byte array to the response without encoding or rendering. It's exactly the same incoming and outgoing traffic, it just finished quicker. > Also, my standard objection to timeouts enters into this. It's on localhost, the longest request takes about 20ms to finish and #sendSomeData:startIndex:count: has a timeout of 20sec. Sending the entire response is four sends to #sendData:count: which is at least four #waitForSendDoneFor: sends. > IMHO, the socket should do what it is asked to do, blocking only the calling thread, and let other threads and/or the user decide when that is taking too long. What does this have to do with replacing a #& with a #and:? > Could you be getting timeouts that are causing unexpected behavior? I don't think so, see above. Since I can't reproduce it anymore it was probably a measuring inaccuracy (~3 %). However I think it's still worthwhile replacing that #&. Cheers Philippe

Nov. 9, 2010

Re: [Pharo-project] Glorp

by Alan Knight

I'm afraid I've been pretty swamped since getting back from ESUG and haven't had a chance to pursue it any further. Real soon now... At 02:28 PM 2010-11-02, Torsten Bergmann wrote: >Hi Alan, (cc pharo list) > >any news from the Glorp relicensing front? > >Thx >Torsten >-- >Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! >Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail -- Alan Knight [|], Engineering Manager, Cincom Smalltalk knight(a)acm.org aknight(a)cincom.com http://www.cincom.com/smalltalk

Nov. 9, 2010

Re: [Pharo-project] Installing Glorp in Pharo 1.1

by Yanni Chiu

On 09/11/10 12:59 PM, glpunzi(a)lordzealon.com wrote: > Hi all, > > I'm trying to install Glorp in Pharo 1.1. I connected to Glorp > Squeaksource repo, and Loaded the GlorpPharoLoader package. Try something like: "GlorpDBX" Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfGlorpDBX'; load. ! ConfigurationOfGlorpDBX ensureMetacello. ! (ConfigurationOfGlorpDBX project version: '1.2') load: { 'All with PostgreSQL native'. }

Nov. 9, 2010

[Pharo-project] [update 1.2] #12231

by StÃ©phane Ducasse

12231 ----- - Issue 3222: saveSession should return its resuming state Marcus apparently the new step for integrating is working. I may integrate some more this evening. Stef

Nov. 9, 2010