- Pharo-dev - lists.pharo.org

[Pharo-project] Which are the limitations of MessageTally?? Re: new Cog VMs uploaded
by Mariano Martinez Peck May 16, 2011

May 16, 2011

What approach do you suggest should I take? >> > > I have no idea. You could try and break down the various activities and > benchmark them separately I suppose. You could look at the profiles you're > already generating in higher resolution to see where the time is going. You > could also try and extract the SystemProfiler from OpenQwaq, which will run > on Cog, and is better than MessageTally. Andreas wrote it to get around > some of MessageTally's limitations. It should hopefully show primitives > quite accurately. > > Hi. I have already read this several times. From you now, from Alexandre Bergel, from Henrik Johansen, etc. But no one (or maybe I didn't see it) give a list of the real existent MessageTally limitations or problems. So far, the only thing I read is what Eliot says here: "show primitives quite accurately" So...which are the rest and what is solved by the SystemProfiler from OpenQwaq ?? Thanks in advance, Mariano > HTH > Eliot > > >> >> Cheers >> Philippe >> >> >> > -- Mariano http://marianopeck.wordpress.com

2 2

[Pharo-project] [COTDC] 64 - UrlArgumentList
by laurent laffont May 16, 2011

May 16, 2011

Today: UrlArgumentList Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

3 4

[Pharo-project] Write accentuate characters in file
by Adrien BARREAU May 16, 2011

May 16, 2011

Hello, A small question I have: how can I write a "Ã©" character in a file and >really< get it in Mac OS? I tried with: FileStream newFileNamed: 'test.txt' do: [ :each | each nextPutAll: 'Ã©Ã©Ã©' ] and got: 'âÂ©âÂ©âÂ©'. I also tried with FileSystem and got : 'ÃÃÃ'. I do not see another way to do that ... Regards, Adrien.

7 8

[Pharo-project] [update 1.3] #13203
by StÃ©phane Ducasse May 16, 2011

May 16, 2011

13203 ----- - Update Zinc fixing support for HTTP proxies (thanks Alexandre Bergel for reporting this) requests to localhost are excluding from being proxied - ZnRequestLine>>#writeOn: now outputs absolute URLs when proxying - added ZnNetWorkingUtils class #isProxySet #shouldProxyUrl: and #httpProxy - added ZnUrl>>#isLocalHost - changed ZnUrl>>#host: to lowerCase its argument. - Fix methodClass - Issue 4237: Few fix for Settings. Thanks Benjamin van Ryseghem. - Issue 4235: Selection update. Thanks Benjamin van Ryseghem.

2 1

[Pharo-project] Support for stdout without OSProcess (issue 4065)
by Stefan Marr May 16, 2011

May 16, 2011

Hi: What needs to be done for issue 4065? http://code.google.com/p/pharo/issues/detail?id=4065 I would like to have an easy way to provide compatibility for the RoarVM primitive RVMOperations>print: which really just dumps a string to stdout. So, ideally, I don't want to many dependencies like OSProcess in SMark. What would need to be done for that? The issue is not to verbose. Is it a missing print primitive in the VM? Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

4 8

[Pharo-project] LAst Phato core, Zn and proxy [WAS] Re: 1.3-Core
by Mariano Martinez Peck May 16, 2011

May 16, 2011

Hi. I didn't follow the long thread, but in latest PharoCore (when Zn is present) I cannot use monticello because I cannot get out. I am behind a proxy but with the previous network library it worked out of the box. Is this the same problem of Alexandre? is there an issue in the bugtracket? can we integrated? is there a workarround so that I can continue using my image? Thanks Mariano On Fri, May 13, 2011 at 3:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > I updated Zinc-HTTP and Zinc-Tests from your server. > Running the tests gives me: 151 run, 151 passes, 0 expected failures, 0 > failures, 0 errors, 0 unexpected passes > > Really cool! > > Alexandre > > On 13 May 2011, at 09:39, Sven Van Caekenberghe wrote: > > > > > On 13 May 2011, at 15:24, Alexandre Bergel wrote: > > > >> I use a core 13197. Running Zinc tests gives me: > >> 146 run, 118 passes, 0 expected failures, 28 failures, 0 errors, 0 > unexpected passes > > > > For all tests to pass, you need the very latest version (160) where the > proxy is bypassed for localhost. > > Also, make sure no other ZnServers are running (they would block the 1701 > port needed by the tests). > > > > Sven > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- Mariano http://marianopeck.wordpress.com

3 4

[Pharo-project] [update 1.3] #13202
by StÃ©phane Ducasse May 16, 2011

May 16, 2011

13202 ----- - Issue 4231: To make sure that we can deprecated RecentMessageSet. - Cleaning FlatBrowser

1 0

Re: [Pharo-project] SSL/HTTPS - SecureSocketStream/SSLSessionforPharo/Squeak and other Smalltalk implementations
by mkobetic＠gmail.com May 16, 2011

May 16, 2011

"Miguel CobÃ¡"<miguel.coba(a)gmail.com> wrote: > But the performance is an issue. And I think that there was a discussion > several years ago that lead to choice a plugin instead of the > all-smalltalk code (independently of the queality of the smalltalk > code). Also a point was made about the maintainability of the smalltalk > code with respect to a library of the underlying OS, with respect to > CERT issues and 0-day exploits. given the few resources in the community > for simpler (relative to crypto) projects like *completion, RB and so, I > think is a wise decision to use the proved, tested and maintained OS > libraries through a plugin part of the standard VM. Of course, the > smalltalk implementation can be used as a fallback for platforms where a > plugin isn't available. These are certainly important things to consider, but I think the arguments need to be more specific and thought through. There are probably dozens of tried and proven libraries for pretty much anything out there, so does that mean there's no point implementing anything? Moreover an external interface is not maintenance free either, they can be surprisingly brittle in many ways and libraries tend to have their own quirks that you may need to accommodate. Anyway, I'd like to focus on the SSL performance argument here. The primary bottleneck of an all-smalltalk SSL implementation are the hashes and symmetric ciphers, which have to chew on every byte of data going through a connection and are too slow in Smalltalk (orders of magnitude slower). The public key algorithms would be the second bottleneck but those are not nearly as bad (more like 5 - 10 times slower depending on the size of the key, and that's primarily because of lack of efficient Integer>>raisedTo:modulo: primitive that peforms well for large integers). Moreover the public key operations happen when a connection is being established, they are not involved in actual data transfer, so long lasting heavily used connections will offset their cost quite easily. To sum up the pub-key ops are no concern on the client, they will likely be a concern on a server (unless it doesn't need to handle many concurrent connections in rapid sequence). So with all that said, I'm confident that a Smalltalk implementation of SSL/TLS can perform as well as any other as long as the hashes and ciphers are farmed out (http://www.cincomsmalltalk.com/userblogs/cst/blogView?printTitle=Xtreams-SS…) Of course that doesn't automatically mean that is should be implemented in Smalltalk. Given that you currently have both available in Squeak (native, Cryptography, and external, SqueakSSL) see how they stack up to each other. How easy are they to configure and use, where do they work and where they don't, do they provide the same features. I'd be curious how the external implementation deals with the issue of verification of the server certificate (I don't mean checking that it's valid, the library can presumably do that for you, but how does the application check that the certificate identifies the entity that it wants to reach?). What about session management (caching, resumption control, load-balancing etc)? Anyway, lots of things to consider indeed. One thing that wrapping an external library usually doesn't give you is thorough understanding of the mechanics and capabilities of the protocol, which is double-plus important with security. You won't get a secure connection if you don't configure/use the protocol correctly. And you have to configure it to some degree, there isn't an appropriate one-size fits all default. Arguably you shouldn't need to actually implement one to get that understanding, but it sure does help a lot :-). My 2c, Martin

4 9

[Pharo-project] squeaksource is down :(
by Mariano Martinez Peck May 16, 2011

May 16, 2011

Thanks -- Mariano http://marianopeck.wordpress.com

2 1

[Pharo-project] [Hudson] update
by Marcus Denker May 16, 2011

May 16, 2011

-> 1.2 and 1.3 (both core and Full) are on the way to be green at the same time for the first time. -> We added some projects to the TaskForces: Ring: https://pharo-ic.lille.inria.fr/hudson/job/Ring/ A new Meta Model for code Fuel: https://pharo-ic.lille.inria.fr/hudson/job/Fuel/ Serializer Nautilus: https://pharo-ic.lille.inria.fr/hudson/job/Nautilus/ Browser Nile: https://pharo-ic.lille.inria.fr/hudson/job/Nile/ Streams, rewritten with Traits (used to be part of Full, parked here until we have manpower to look at it and push it...) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0