May 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Basic tricks for improving a serializer?

by Sven Van Caekenberghe

On 17 May 2011, at 22:58, Mariano Martinez Peck wrote: > yeah, I was trying that. Just by curious, why you put a 2^X number there? Because I am a computer geek.

May 17, 2011

Re: [Pharo-project] Filesystem-cwp.120 is broken

by StÃ©phane Ducasse

tx doru When the stone gets rolling dropping it means that you have to put energy back into it to make it roll again, so I will restart it when I get back energy. Stef > Hi, > > A month ago I sent an email documenting the changes (including the update to the configuration): > http://lists.gforge.inria.fr/pipermail/pharo-project/2011-April/046446.html > > Cheers, > Doru > > > On 17 May 2011, at 20:00, StÃ©phane Ducasse wrote: > >> I have to check if we update the configurationOfFS. >> Now I should say that I lost energy in the FS story so we will see how we sort that out. >> >> Stef >> >> On May 17, 2011, at 5:15 PM, Esteban Lorenzano wrote: >> >>> ouch! :) >>> >>> El 17/05/2011, a las 9:47a.m., Lukas Renggli escribiÃ³: >>> >>>>> I just downloaded Filesystem-cwp.120... it is empty, and that makes ConfigurationOfFilesystem to not load correctly. >>>> >>>> If you read the comment of Filesystem-cwp.120 you see that this is >>>> intentional. The package was split quite some time ago into various >>>> independent ones. >>>> >>>> Lukas >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>> >>> >> >> > > -- > www.tudorgirba.com > > "To lead is not to demand things, it is to make them happen." > > > >

May 17, 2011

Re: [Pharo-project] Basic tricks for improving a serializer?

by Mariano Martinez Peck

On Tue, May 17, 2011 at 10:31 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 17 May 2011, at 21:57, Mariano Martinez Peck wrote: > > > Sven, I want to make it work :) > > > > so....the missing methods I told you that I need are: > > > > #nextStringPut: > > #nextNumber:put: > > #nextInt32Put: > > #nextWordPut: > > I guess these are pretty easy. But I think they clutter the interface of > ZnBufferedWriteStream, so maybe you should make a subclass. > > Yeah, don't worry. I can even duplicate the class hehehe > > #contents > > > > Implement #contents I guess it is something like: > > > > ZnBufferedWriteStream >> contents > > ^ stream contents > > Why to you need #contents ? becasue I am an idiot. No, I don't need it. You are correct. Thanks for asking. > I would say that it goes a bit against the concept of a stream as a sink of > data. > I haven't looked, but I would guess that saying #contents to a FileStream > is not efficient. > > > Those missing methods I need are implemented PositionableStream. I took > the implementation from there and put it in ZnBufferedWriteStream. > > I just added to them a first line " self flushBufferIfFull." > > That is probably OK, except when your string becomes larger than the > buffer. Have a look at #nextPutAll: > > I am not sure if I understood. The following are correct for sure then: #nextNumber:put: #nextInt32Put: #nextWordPut: And #nextStringPut: is like this: nextStringPut: s "Append the string, s, to the receiver. Only used by DataStream. Max size of 64*256*256*256." | length | self flushBufferIfFull. (length := s size) < 192 ifTrue: [self nextPut: length] ifFalse: [self nextPut: (length digitAt: 4)+192. self nextPut: (length digitAt: 3). self nextPut: (length digitAt: 2). self nextPut: (length digitAt: 1)]. self nextPutAll: s asByteArray. ^s which will finally send #nextPutAll: that does correct check. > > The way I am creating it is like this: > > > > stream := ZnBufferedWriteStream on: ((FileDirectory default > forceNewFileNamed: 'mariano') binary). > > > > So...is this correct Sven? My tests are green :) > > That seems OK > Ok. > > > Still need to try benchmarks. > > You might also consider playing with making the buffer larger. > > yeah, I was trying that. Just by curious, why you put a 2^X number there? Ahh and for reading we don't need something special because it is already buffered? (I have been told that) Thanks a lot Sven, -- Mariano http://marianopeck.wordpress.com

May 17, 2011

Re: [Pharo-project] [Esug-list] [ANN] SmallHarbour project

by Dale Henrichs

On 05/17/2011 12:37 PM, Davorin Rusevljan wrote: > On Tue, May 17, 2011 at 9:19 PM, laurent laffont > <laurent.laffont(a)gmail.com> wrote: >> Actually we have several visions (nothing is final here, ideas welcome) > .. > > Having Amazon ec2 image is also a very good idea, and some > Smalltalkers have already made first important steps like: > > http://www.nickager.com/blog/Create-a-free-Gemstone-server-in-the-cloud-in-… > > You probably already have enough on your plate, but I mentioned > CloudFoundry for following reasons: > - it has a promise that one would be able to deploy SmallHarbour to > different cloud providers > - CloudFoundry currently provides support for Java, Ruby and > Javascript, adding Smalltalk would be nice for visibility, and could > be used for other Smalltalk services not only SmallHarbour. > > As I said you probably have enough to do in the first place, but if > you just happen to have some student lurking that has some ruby > knowledge to hack the interface for Smalltalk to Cloudfoundry it would > be very nice to have :) > > As for your other goals - great! > > Davorin Rusevljan > http://www.cloud208.com/ > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org Laurent/Davorin, We are in the process of adding support for deploying GLASS applications into the Cloud Foundry, but I wouldn't mind helping folks who are interested in adding support for other Smalltalks into the Cloud Foundry ... The Cloud Foundry is written largely in ruby, so you'll need to be wearing your ruby dancing shoes:) Dale

May 17, 2011

Re: [Pharo-project] I give up. Squeaksource has lost lot ofversions again

by laurent laffont

On Tue, May 17, 2011 at 10:39 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Is squeaksource stable again? > can I commit files? May the force be with you ;) Laurent. > > > On Tue, May 17, 2011 at 4:50 PM, Bernat Romagosa < > tibabenfortlapalanca(a)gmail.com> wrote: > >> I don't understand why is there a thread identical to this one every two >> or three weeks. This discussion was already held a long time ago and its >> outcome was that someone was hired to implement a new code repository, >> Smalltalkhub's the name. >> >> This problem is in its way to be permanently solved, let's all stop >> speculating about how the system will be and how great would it be if it had >> feature X. I'm sure Smalltalkhub will be _miles_ ahead of Squeaksource and >> we'll all be able to contribute our ideas once it is up, running and being >> actively tested. Of course I expect ESUG thought not only of getting it >> implemented but also of its maintenance, so I propose we just wait for it to >> come out and bury this fruitless discussion once and for all. >> >> In the meantime, I guess we all have to be patient and keep putting up >> with an obsolete system for a little bit longer. >> >> Cheers, >> >> Bernat >> > > > > -- > Mariano > http://marianopeck.wordpress.com > >

May 17, 2011

Re: [Pharo-project] I give up. Squeaksource has lost lot ofversions again

by Mariano Martinez Peck

Is squeaksource stable again? can I commit files? On Tue, May 17, 2011 at 4:50 PM, Bernat Romagosa < tibabenfortlapalanca(a)gmail.com> wrote: > I don't understand why is there a thread identical to this one every two or > three weeks. This discussion was already held a long time ago and its > outcome was that someone was hired to implement a new code repository, > Smalltalkhub's the name. > > This problem is in its way to be permanently solved, let's all stop > speculating about how the system will be and how great would it be if it had > feature X. I'm sure Smalltalkhub will be _miles_ ahead of Squeaksource and > we'll all be able to contribute our ideas once it is up, running and being > actively tested. Of course I expect ESUG thought not only of getting it > implemented but also of its maintenance, so I propose we just wait for it to > come out and bury this fruitless discussion once and for all. > > In the meantime, I guess we all have to be patient and keep putting up with > an obsolete system for a little bit longer. > > Cheers, > > Bernat > -- Mariano http://marianopeck.wordpress.com

May 17, 2011

Re: [Pharo-project] Basic tricks for improving a serializer?

by Sven Van Caekenberghe

On 17 May 2011, at 21:57, Mariano Martinez Peck wrote: > Sven, I want to make it work :) > > so....the missing methods I told you that I need are: > > #nextStringPut: > #nextNumber:put: > #nextInt32Put: > #nextWordPut: I guess these are pretty easy. But I think they clutter the interface of ZnBufferedWriteStream, so maybe you should make a subclass. > #contents > > Implement #contents I guess it is something like: > > ZnBufferedWriteStream >> contents > ^ stream contents Why to you need #contents ? I would say that it goes a bit against the concept of a stream as a sink of data. I haven't looked, but I would guess that saying #contents to a FileStream is not efficient. > Those missing methods I need are implemented PositionableStream. I took the implementation from there and put it in ZnBufferedWriteStream. > I just added to them a first line " self flushBufferIfFull." That is probably OK, except when your string becomes larger than the buffer. Have a look at #nextPutAll: > The way I am creating it is like this: > > stream := ZnBufferedWriteStream on: ((FileDirectory default forceNewFileNamed: 'mariano') binary). > > So...is this correct Sven? My tests are green :) That seems OK > Still need to try benchmarks. You might also consider playing with making the buffer larger. Sven

May 17, 2011

[Pharo-project] Zodiac - 1st delivery - A new (binary) socket stream

by Sven Van Caekenberghe

Hi, I would like to announce Zodiac, the project created in response to http://forum.world.st/WebClient-for-1-2-2-tt3485946.html#a3503921 according to the plan described in http://forum.world.st/SSL-HTTPS-SecureSocketStream-SSLSession-for-Pharo-Squ… You can follow the development by looking at the code in http://www.squeaksource.com/Zodiac.html Here is the first delivery: a new (binary) socket stream implementation. Warning: this is of course not yet code for general consumption, use the source and the comments. This is a proof of concept. This package has no further dependencies and does not add anything to system classes, it is thus safe to load. There are four stream classes, ZdcAbstractSocketStream, ZdcSimpleSocketStream, ZdcOptimizedSocketStream and ZdcSocketStream, inheriting from each other, adding successively more optimized implementations of the standard Smalltalk stream primitives. There is one helper class, ZdcIOBuffer to help in managing read and write buffers inside the streams. The interface towards Socket is also quite small (i.e. only a very small amount of the functionality in Socket is used). The 48 units tests as well as the functional test (see further) are all green on Pharo 1.2.x and 1.3 as well as on Squeak 4.2. The functional test is the following: Zinc HTTP Components recently got a its ZnNetworkingUtils class turned into a socket stream factory. By loading the new package Zinc-Zodiac from the ZincHTTPComponents repository, you can ask Zn to use the new socket stream implementation, like this: ZnNetworkingUtils default: ZnZodiacNetworkingUtils new. To reset, just do: ZnNetworkingUtils default: nil. The cool thing is: all of Zn's 151 unit tests, most doing actual HTTP client and server interactions (some over the internet) succeed using the new Zodiac socket stream implementation. Enjoy! Sven

May 17, 2011

Re: [Pharo-project] [Esug-list] [ANN] SmallHarbour project

by Mariano Martinez Peck

On Tue, May 17, 2011 at 9:46 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > On Tue, May 17, 2011 at 9:43 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Tue, May 17, 2011 at 9:41 PM, laurent laffont < >> laurent.laffont(a)gmail.com> wrote: >> >>> On Tue, May 17, 2011 at 9:29 PM, Mariano Martinez Peck < >>> marianopeck(a)gmail.com> wrote: >>> >>>> Hi Laurent. You should take a look to GLASS applicance. >>>> It is similar to what you want. You can take ideas from there. >>>> >>> >>> Yes, good idea to have a look. >>> >>> I actually wonder which database support should come out of the box. >>> >>> >> Do it directly on top of Glass and you already have a lot of things for >> free, included that question ;) >> > > I would like all the stack to be open source. Gemstone isn't ? > > No. It is not. It is free with certain conditions, but not Open Source. > Laurent. > > > > >> You only need to implement the logistic for the app (kind of >> seasidehosting). >> > >> >>> Laurent. >>> >>> >>> >>>> BTW, cool project and congrats! >>>> >>>> mariano >>>> >>>> >>>> On Tue, May 17, 2011 at 9:19 PM, laurent laffont < >>>> laurent.laffont(a)gmail.com> wrote: >>>> >>>>> On Tue, May 17, 2011 at 8:27 PM, Davorin Rusevljan < >>>>> davorin.rusevljan(a)gmail.com> wrote: >>>>> >>>>>> Interesting! >>>>>> >>>>>> Have you maybe considered to base it on the cloud foundry? >>>>>> >>>>> >>>>> Actually we have several visions (nothing is final here, ideas welcome) >>>>> >>>>> 1/ SmallHarbour platform is meant to be a base for YOUR own hosting >>>>> platform, like your own seaside hosting. So whether you put it on the cloud >>>>> or on a real server should be a preference. >>>>> >>>>> Actually we don't have any experience with cloud, so help will be >>>>> appreciated. >>>>> >>>>> We plan to have a virtual appliance based on virtual box / vmware /.... >>>>> for an easy setup. Amazon VMI image should be a good idea too (we have to >>>>> learn). >>>>> >>>>> For example: >>>>> a / I work in an enterprise, I want to easily deploy Smalltalk web >>>>> applications / tools on intranet for my co-workers and I don't want to spend >>>>> time on setting up servers, apache, ...... So I could just get the >>>>> appliance, start it and I'm ready to deploy several images. >>>>> >>>>> b / I want to set up a unique VPS (or cloud platform) to deploy several >>>>> Smalltalk web apps / sites. I could just put my preferred Linux distro, then >>>>> >>>>> apt-get install smallharbour / pacman -s smallharbour / .... >>>>> >>>>> /etc/rc.d/smallharbour start >>>>> >>>>> and let's go ! >>>>> >>>>> >>>>> 2/ SmallHarbour hosting service which be like SeasideHosting, but for >>>>> commercial purposes. So you should create an account, pay a monthly / yearly >>>>> fee related to the service you want, then either >>>>> >>>>> a/ upload your own image (like you do for SeasideHosting) if you're a >>>>> power user >>>>> >>>>> b/ one-click deploy of pre-made image if you just want to setup a CMS, >>>>> blog, write a new book, event planing, ... Pre-made images should be updated >>>>> easily. >>>>> >>>>> >>>>> 3/ People who need scalability, performance, deep customization don't >>>>> need SmallHarbour :) >>>>> >>>>> >>>>> Laurent >>>>> >>>>> Davorin Rusevljan >>>>>> http://www.cloud208.com/ >>>>>> >>>>>> On May 17, 2011 6:26 PM, "laurent laffont" <laurent.laffont(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> On Tue, May 17, 2011 at 5:29 PM, Bernat Romagosa < >>>>>> tibabenfortlapalanca(a)gmail.com> wrote: >>>>>> > >>>>>> > Just a ... >>>>>> >>>>>> Yes, that's why we haven't called it SeasideSomething. >>>>>> >>>>>> We want the project to be open and support several web frameworks. We >>>>>> will start with Seaside though. >>>>>> >>>>>> Laurent. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> > >>>>>> > >>>>>> > 2011/5/17 Romain Verduci <contact(a)romain-verduci.com> >>>>>> >> >>>>>> >> We actually have www.seasideho... >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Esug-list mailing list >>>>>> Esug-list(a)lists.esug.org >>>>>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Esug-list mailing list >>>>> Esug-list(a)lists.esug.org >>>>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>>>> >>>>> >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > -- Mariano http://marianopeck.wordpress.com

May 17, 2011

Re: [Pharo-project] Basic tricks for improving a serializer?

by Mariano Martinez Peck

Sven, I want to make it work :) so....the missing methods I told you that I need are: #nextStringPut: #nextNumber:put: #nextInt32Put: #nextWordPut: #contents Implement #contents I guess it is something like: ZnBufferedWriteStream >> contents ^ stream contents Those missing methods I need are implemented PositionableStream. I took the implementation from there and put it in ZnBufferedWriteStream. I just added to them a first line " self flushBufferIfFull." The way I am creating it is like this: stream := ZnBufferedWriteStream on: ((FileDirectory default forceNewFileNamed: 'mariano') binary). So...is this correct Sven? My tests are green :) Still need to try benchmarks. Thanks! Mariano On Tue, May 17, 2011 at 8:18 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Tue, May 17, 2011 at 3:34 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > >> Mariano, >> >> On 17 May 2011, at 15:21, Mariano Martinez Peck wrote: >> >> > Now Igor told us for example, to use a buffer like this: >> > >> > | bufferStream | >> > bufferStream := ByteArray new writeStream. >> > >> > (FLSerializer on: bufferStream) >> > serialize: anArrayToSerialize. >> > >> > aFileStream nextPutAll: bufferStream contents. >> > >> > and that it at least 2 times faster than we were doing.... I guess it is >> because it goes to the disk only once. But MultiByteFileStream uses a >> buffer, doesn't it ? >> >> The disadvantage of the above is that you buffer everything before you >> write. Furthermore you are growing the buffer all the time (recopying >> contents) which is not too efficient. >> >> Some time ago we had a discussion about this and then I implemented >> ZnBufferedWriteStream (it should be in Core 1.3), have a look. It was just a >> quick hack, but it worked in speeding up writing. >> >> > Thanks Sven, what a great point you gave me. I tried it a little and I > found a couple of methods missing which I used to use for a normal > WriteStream. > I will play a little more when I have time and I will ask you again!! > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 17, 2011