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

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

by Sven Van Caekenberghe

Hi Luc, On 18 May 2011, at 08:00, Luc Fabresse wrote: > That's a really really news. > I look forward when we will reach a stable point for Ocean to use Zodiac on top of it. > FYI, Ocean is a re-implementation of Sockets (Netnameresolver, IpAddress, ....). As I said the interface towards Socket is quite small, it should be really easy to plug in an alternative. Apart from connect/disconnect and isConnected/isDataAvailable there are two key methods: ZdcSimpleSocketStream>>fillBytes: bytes startingAt: offset count: count "Ask the socket to read count elements into bytes starting at offset. Do not wait. Return read count." ZdcSimpleSocketStream>>flushBytes: bytes startingAt: offset count: count "Ask the socket to write count bytes starting from offset. Wait. Fail if not successful" And then there is the logic to wait for input. The optimized versions build on this interface. Sven

May 18, 2011

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

by Andreas Raab

On 5/17/2011 22:24, Sven Van Caekenberghe wrote: > 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… Some comments: > BTW, It will be (very) hard to get Pharo+WebClient+SSL+MacOSX working. Not really. I just don't have a Mac, so all my Mac work is done in the few hours that I actually have access to one. The stuff that's missing in the Mac version of SqueakSSL isn't hard given a couple of days and a Mac and WebClient ran fine on Pharo last time I tried it. > - why was it [Cryptography] not used for SqueakSSL ? Because the stated goal of SqueakSSL is to use the native platform bindings for SSL on each platform. For reasons of a) performance, b) upgradability, c) compliance, and d) size of implementation. FWIW, I'm not sure I follow your reasoning regarding Zodiac. As it stands, there are two working implementation of SSL: SqueakSSL and Cryptography. You could just use one of the two and contribute to either development if there are things you don't like about them. Cheers, - Andreas

May 18, 2011

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

by Luc Fabresse

Hi Sven, That's a really really news. I look forward when we will reach a stable point for Ocean to use Zodiac on top of it. FYI, Ocean is a re-implementation of Sockets (Netnameresolver, IpAddress, ....). Cheers, #Luc 2011/5/17 Sven Van Caekenberghe <sven(a)beta9.be> > 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 18, 2011

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

by laurent laffont

On Tue, May 17, 2011 at 10:48 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > 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:) > Thanks Dale, just need to wax my shoes first, haven't worn them for a long time :) Laurent. > > Dale >

May 18, 2011

Re: [Pharo-project] Error loading update with AnObsoleteTranscript

by Alain_Rastoul

Thanks Mariano It did it for a while (twice because of 'context not in process chain' errors). Then I had a ***system error handling failed*** Original error: Error MNU: TextAttribute class>> colorBlock: Debugger error: SubscriptOutOfBounds ... etc message on top line of Pharo's main window (I had switched to another window then returned to Pharo window again) I 'll try again tomorrow :o) Cheers Alain "Mariano Martinez Peck" <marianopeck(a)gmail.com> a Ã©crit dans le message de news: BANLkTim2exeJ5=--Nfm-oegmjxV1xQqy6A(a)mail.gmail.com... ahahahahhaha HAHAHAHAHAHAHAHAHHAHAHH SmalltalkImage >> fixObsoleteReferences "SmalltalkImage current fixObsoleteReferences. SystemNavigation default obsoleteBehaviors size > 0 ifTrue: [ SystemNavigation default obsoleteBehaviors inspect. self error:'Still have obsolete behaviors. See inspector']" | informee obsoleteBindings obsName realName realClass | Smalltalk garbageCollect; garbageCollect. CompiledMethod allInstances do: [ :method | obsoleteBindings := method literals select: [ :literal | literal isVariableBinding and: [ literal value isBehavior and: [ literal value isObsolete ]]]. obsoleteBindings do: [ :binding | obsName := binding value name. Transcript show: 'Binding: '; show: obsName; cr. realName := obsName copyReplaceAll: 'AnObsolete' with: ''. realClass := Smalltalk globals at: realName asSymbol ifAbsent: [ UndefinedObject ]. binding key: binding key value: realClass ] ]. Behavior flushObsoleteSubclasses. Smalltalk garbageCollect; garbageCollect remove that lines in yellow and try again :) On Wed, May 18, 2011 at 12:30 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: When I do Smalltalk fixObsoleteReferences I have AnObsoleteTranscript class DNU show: :( "Mariano Martinez Peck" <marianopeck(a)gmail.com> a Ã©crit dans le message de news: BANLkTin_Q9ArEvU6qHZRcT2x9r3VLFp39w-JsoAwUIsXosN+BqQ9rBEUg(a)public.gmane.org... On Wed, May 18, 2011 at 12:06 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: Hi, Trying to upgrade my 1.3 image with Menu/System/Software Update, I had a MNU during update 13191 at AnObsoleteTranscript class >> cr which comes from: UndeclaredVariableWarning>>defaultAction selector ifNotNil: [Transcript cr; nextPutAll: class name, '>>', selector, ' '] ifNil: [Transcript cr ]. Transcript show: '(' , name , ' is Undeclared) '. ^true Something is missing or I did something wrong? Probably not. But probably Smalltalk fixObsoleteReferences also fixes it. TIA Regards, Alain -- Mariano http://marianopeck.wordpress.com -- Mariano http://marianopeck.wordpress.com

May 17, 2011

Re: [Pharo-project] Error loading update with AnObsoleteTranscript

by Mariano Martinez Peck

ahahahahhaha HAHAHAHAHAHAHAHAHHAHAHH SmalltalkImage >> fixObsoleteReferences "SmalltalkImage current fixObsoleteReferences. SystemNavigation default obsoleteBehaviors size > 0 ifTrue: [ SystemNavigation default obsoleteBehaviors inspect. self error:'Still have obsolete behaviors. See inspector']" | informee obsoleteBindings obsName realName realClass | Smalltalk garbageCollect; garbageCollect. CompiledMethod allInstances do: [ :method | obsoleteBindings := method literals select: [ :literal | literal isVariableBinding and: [ literal value isBehavior and: [ literal value isObsolete ]]]. obsoleteBindings do: [ :binding | obsName := binding value name. Transcript show: 'Binding: '; show: obsName; cr. realName := obsName copyReplaceAll: 'AnObsolete' with: ''. realClass := Smalltalk globals at: realName asSymbol ifAbsent: [ UndefinedObject ]. binding key: binding key value: realClass ] ]. Behavior flushObsoleteSubclasses. Smalltalk garbageCollect; garbageCollect remove that lines in yellow and try again :) On Wed, May 18, 2011 at 12:30 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: > When I do Smalltalk fixObsoleteReferences I have > AnObsoleteTranscript class DNU show: > :( > > "Mariano Martinez Peck" <marianopeck(a)gmail.com> a Ã©crit dans le message de > news: BANLkTin_Q9ArEvU6qHZRcT2x9r3VLFp39w(a)mail.gmail.com... > > > On Wed, May 18, 2011 at 12:06 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: > >> Hi, >> >> Trying to upgrade my 1.3 image with Menu/System/Software Update, >> I had a MNU during update 13191 at >> AnObsoleteTranscript class >> cr >> which comes from: >> UndeclaredVariableWarning>>defaultAction >> selector ifNotNil: [Transcript cr; nextPutAll: class name, '>>', >> selector, >> ' '] >> ifNil: [Transcript cr ]. >> Transcript show: '(' , name , ' is Undeclared) '. >> ^true >> >> Something is missing or I did something wrong? >> >> > Probably not. But probably Smalltalk fixObsoleteReferences also fixes it. > > > >> TIA >> Regards, >> Alain >> >> >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 17, 2011

Re: [Pharo-project] Error loading update with AnObsoleteTranscript

by Alain_Rastoul

When I do Smalltalk fixObsoleteReferences I have AnObsoleteTranscript class DNU show: :( "Mariano Martinez Peck" <marianopeck(a)gmail.com> a Ã©crit dans le message de news: BANLkTin_Q9ArEvU6qHZRcT2x9r3VLFp39w(a)mail.gmail.com... On Wed, May 18, 2011 at 12:06 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: Hi, Trying to upgrade my 1.3 image with Menu/System/Software Update, I had a MNU during update 13191 at AnObsoleteTranscript class >> cr which comes from: UndeclaredVariableWarning>>defaultAction selector ifNotNil: [Transcript cr; nextPutAll: class name, '>>', selector, ' '] ifNil: [Transcript cr ]. Transcript show: '(' , name , ' is Undeclared) '. ^true Something is missing or I did something wrong? Probably not. But probably Smalltalk fixObsoleteReferences also fixes it. TIA Regards, Alain -- Mariano http://marianopeck.wordpress.com

May 17, 2011

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

by Igor Stasenko

On 17 May 2011 22:58, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > 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 > Sorry, but i can't resist commenting on that. Why, if you demand from stream to implement #nextInt32Put: a the same time, you writing code like this self nextPut: (length digitAt: 4)+192. self nextPut: (length digitAt: 3). self nextPut: (length digitAt: 2). self nextPut: (length digitAt: 1) ? Then just extend your serializer with a notion of 'length' field, which you can use for anything where you need to encode length/size value, but not just for Strings. So, then the above method could be as short as: nextStringPut: s self putLength: s size. self nexPutAll: s asByteArray. and here you have a potential caveat because your string could be WideString .. muhahaha. So, i suggest you to reconsider the way how you serializing strings. Instead what you could do is to extend ByteString and WideString (and perhaps similarily do for ByteSymbol and WideSymbol), the methods which is responsible to turning a receiver in a sequence of bytes, and then simply put it into output stream, whatever it might be. Then you don't need #nextStringPut: because its a) not polymorphic, because apparently serializing ByteString should be different from serializing WideString b) instead you implementing this in Byte/WideString>>serializeToFuelStream: aStream and you done. > > 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 > > -- Best regards, Igor Stasenko AKA sig.

May 17, 2011

Re: [Pharo-project] Error loading update with AnObsoleteTranscript

by Mariano Martinez Peck

On Wed, May 18, 2011 at 12:06 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: > Hi, > > Trying to upgrade my 1.3 image with Menu/System/Software Update, > I had a MNU during update 13191 at > AnObsoleteTranscript class >> cr > which comes from: > UndeclaredVariableWarning>>defaultAction > selector ifNotNil: [Transcript cr; nextPutAll: class name, '>>', selector, > ' '] > ifNil: [Transcript cr ]. > Transcript show: '(' , name , ' is Undeclared) '. > ^true > > Something is missing or I did something wrong? > > Probably not. But probably Smalltalk fixObsoleteReferences also fixes it. > TIA > Regards, > Alain > > > > > -- Mariano http://marianopeck.wordpress.com

May 17, 2011

[Pharo-project] Error loading update with AnObsoleteTranscript

by Alain_Rastoul

Hi, Trying to upgrade my 1.3 image with Menu/System/Software Update, I had a MNU during update 13191 at AnObsoleteTranscript class >> cr which comes from: UndeclaredVariableWarning>>defaultAction selector ifNotNil: [Transcript cr; nextPutAll: class name, '>>', selector, ' '] ifNil: [Transcript cr ]. Transcript show: '(' , name , ' is Undeclared) '. ^true Something is missing or I did something wrong? TIA Regards, Alain

May 17, 2011