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

Re: [Pharo-project] Status of WebClient for Pharo?

by GermÃ¡n Arduino

I use WebClient on Pharo with no problems, in productions customers. In 2 cases were I needed SSL, I used WebClient in Squeak with the SSL plugin also with no problems. I should try again the SSL plugin in Pharo, but not time at the moment. Cheers. 2011/4/16 Jan van de Sandt <jvdsandt(a)gmail.com>: > Hello Friedrich, > I used WebClient and SqueakSSL om Pharo 1.1 a few months ago. WebClient > works but SqueakSSL had some problems. It didn't work with some hosts (like > Yahoo) and some features were missing on OSX. > Now I use Zinc HTTP as a web client on Pharo. For SSL support I use stunnel. > This needs some setup but works very well [1]. > Jan. > [1]Â http://blog.doit.st/2011/02/23/cloudforksso-on-pharo-with-stunnel/ > > On Sat, Apr 16, 2011 at 6:56 PM, Friedrich Dominicus > <frido(a)q-software-solutions.de> wrote: >> >> Dear Pharo developers, can you tell me about the status of WebClient in >> Pharo. (well and if you know it would be nice to know if SqueakSSL is >> "working", or "working in principal" or "not working.) >> >> Or do you have other suggestions for accessing the diverse Web services >> with Pharo? >> >> Regards >> Friedrich >> > >

April 16, 2011

Re: [Pharo-project] About Zinc to replace HTTPClient

by GermÃ¡n Arduino

2011/4/16 Jan van de Sandt <jvdsandt(a)gmail.com>: > Hello, > Yes, CloudforkSSO has support for OAuth1, AOuth2 and OpenID. Cloudfork uses > Zinc as HTTP client library. Works very well. > Indeed, SSL is not supported directly. But using stunnel [1] is a good > workaround for this. Yes I understand your and Norbert point but, as you comment is a workaround. I honestly prefer the way of WebClient, when only need to have a plugin, but may be are different visions. Cheers.

April 16, 2011

Re: [Pharo-project] Status of WebClient for Pharo?

by Jan van de Sandt

Hello Friedrich, I used WebClient and SqueakSSL om Pharo 1.1 a few months ago. WebClient works but SqueakSSL had some problems. It didn't work with some hosts (like Yahoo) and some features were missing on OSX. Now I use Zinc HTTP as a web client on Pharo. For SSL support I use stunnel. This needs some setup but works very well [1]. Jan. [1] http://blog.doit.st/2011/02/23/cloudforksso-on-pharo-with-stunnel/ On Sat, Apr 16, 2011 at 6:56 PM, Friedrich Dominicus < frido(a)q-software-solutions.de> wrote: > Dear Pharo developers, can you tell me about the status of WebClient in > Pharo. (well and if you know it would be nice to know if SqueakSSL is > "working", or "working in principal" or "not working.) > > Or do you have other suggestions for accessing the diverse Web services > with Pharo? > > Regards > Friedrich > >

April 16, 2011

Re: [Pharo-project] About Zinc to replace HTTPClient

by Jan van de Sandt

Hello, Yes, CloudforkSSO has support for OAuth1, AOuth2 and OpenID. Cloudfork uses Zinc as HTTP client library. Works very well. Indeed, SSL is not supported directly. But using stunnel [1] is a good workaround for this. Jan. [1] http://blog.doit.st/2011/02/23/cloudforksso-on-pharo-with-stunnel/ On Sat, Apr 16, 2011 at 5:37 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 16.04.2011 um 15:13 schrieb GermÃ¡n Arduino: > > > I would like to know exactly what features will provide Zn and which not. > > > What do you mean with features? > > > As I remember form the past was not planned to support for example > > https, which prevent to use OAuth and OpenID, very needed to develop > > any interaction against any modern web site. > > > Zinc is http handling components. Https is just a http request over a > transparently initiated SSL connection. So if you have SSL you have https. > It is not the duty of an http component to support SSL. A url handler needs > to integrate existing SSL. > As far as I remember the cloudfork guys have OAuth running. So they must > have SSL. So it shouldn't be to hard to do the same with zinc. Just exchange > the http handling routines. > > Norbert > > > 2011/4/16 Norbert Hartl <norbert(a)hartl.name>: > >> > >> Am 15.04.2011 um 22:12 schrieb StÃ©phane Ducasse: > >> > >>> Hi guys > >>> > >>> we discuss with sven about strategies to get a better infrastructure > and the HTTP level. > >>> Sven would like to have feedback on Zinc before pushing it in Pharo :) > >>> So can you let us know. What we could do it to have it in a preview in > 1.3 > >>> then in 1.4 remove HTTPClient (or friend). > >> > >> This is really good. To me (meaning IMHO) it is one of the most missing > functionalities in pharo. Zinc is really great and so much better than > _anything_ in pharo that pretends to do HTTP. I would like to see it that we > don't talk about HTTP but about proper MIME based communication. I think the > very core that is in there is the structured and flexible mime media > handling and communication. And this is not only true for HTTP but also for > email. > >> I would like to see that Zinc creeping into the image bringing the mime > stuff along. Than the mime stuff should break loose of the Zinc components > and should replace the mime handling that is in the image. Than we have it > for http and for mail sending and for every other transport protocol you can > imagine. > >> And now that Paul ported zinc to gemstone you can develop good http > handlers that are easily ported to gemstone. What a wonderful world! > >> And seaside? Well, if the current http adaptors are much faster than > zinc than there should be shortcut path through zinc that allows fast > handling of the minimal stuff seaside needs. The same problem goes for the > WARequest stuff. Using zinc you can get access to the mime parts. Now > WARequest is a strange request object that contains a dictionary for request > parameters and a raw message body. If only compatibility is important than a > zinc to old WARequest handling is needed. But I would like to see the mime > based handling to be the "normal" way of doing and not vice versa. But I can > see that it must be a special treatment as seaside is ported to so many > platforms that don't have zinc. Probably one reasone more to extract the > mime stuff. It might be a promininent candidate other platforms adopt. > >> > >> my two cents, > >> > >> Norbert > >> > >> > >> > > > > >

April 16, 2011

Re: [Pharo-project] Desktop application with Pharo

by Helene Bilbo

laurent laffont wrote: > > I'm searching for a way to create desktop applications with Pharo (no > multiple window). > Hi. While i can't contribute anything, i just wanted to tell you that i'm very interested in this. Please continue posting your findings :) Best regards, Helene. -- View this message in context: http://forum.world.st/Desktop-application-with-Pharo-tp3453812p3454314.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 16, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #14 on issue 3545 by marcus.d...(a)gmail.com: FEATURE: Multiple Worlds http://code.google.com/p/pharo/issues/detail?id=3545 not for 1.3

April 16, 2011

Re: [Pharo-project] Issue 4028 in pharo: Possible infinite loop in ImageSegment >> #uniqueFileNameFor:

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #3 on issue 4028 by marcus.d...(a)gmail.com: Possible infinite loop in ImageSegment >> #uniqueFileNameFor: http://code.google.com/p/pharo/issues/detail?id=4028 Not a showstopper for 1.3

April 16, 2011

Re: [Pharo-project] Issue 3981 in pharo: #<= on SourcedMethodReference is very slow

by pharo＠googlecode.com

Updates: Status: Closed Comment #8 on issue 3981 by marcus.d...(a)gmail.com: #<= on SourcedMethodReference is very slow http://code.google.com/p/pharo/issues/detail?id=3981 in 13159

April 16, 2011

Re: [Pharo-project] About Zinc to replace HTTPClient

by Norbert Hartl

Am 16.04.2011 um 15:13 schrieb GermÃ¡n Arduino: > I would like to know exactly what features will provide Zn and which not. > > As I remember form the past was not planned to support for example > https, which prevent to use OAuth and OpenID, very needed to develop > any interaction against any modern web site. > Btw. if you want to use OAuth etc. you usually only need outbound SSL to one or a few hosts. For this you can use a webserver like nginx that does proxy pass to a SSL host or you can use stunnel on the machine that does the SSL wrapper. There are a few people reading this list which do exactly this :) Norbert > Cheers. > GermÃ¡n. > > > 2011/4/16 Norbert Hartl <norbert(a)hartl.name>: >> >> Am 15.04.2011 um 22:12 schrieb StÃ©phane Ducasse: >> >>> Hi guys >>> >>> we discuss with sven about strategies to get a better infrastructure and the HTTP level. >>> Sven would like to have feedback on Zinc before pushing it in Pharo :) >>> So can you let us know. What we could do it to have it in a preview in 1.3 >>> then in 1.4 remove HTTPClient (or friend). >> >> This is really good. To me (meaning IMHO) it is one of the most missing functionalities in pharo. Zinc is really great and so much better than _anything_ in pharo that pretends to do HTTP. I would like to see it that we don't talk about HTTP but about proper MIME based communication. I think the very core that is in there is the structured and flexible mime media handling and communication. And this is not only true for HTTP but also for email. >> I would like to see that Zinc creeping into the image bringing the mime stuff along. Than the mime stuff should break loose of the Zinc components and should replace the mime handling that is in the image. Than we have it for http and for mail sending and for every other transport protocol you can imagine. >> And now that Paul ported zinc to gemstone you can develop good http handlers that are easily ported to gemstone. What a wonderful world! >> And seaside? Well, if the current http adaptors are much faster than zinc than there should be shortcut path through zinc that allows fast handling of the minimal stuff seaside needs. The same problem goes for the WARequest stuff. Using zinc you can get access to the mime parts. Now WARequest is a strange request object that contains a dictionary for request parameters and a raw message body. If only compatibility is important than a zinc to old WARequest handling is needed. But I would like to see the mime based handling to be the "normal" way of doing and not vice versa. But I can see that it must be a special treatment as seaside is ported to so many platforms that don't have zinc. Probably one reasone more to extract the mime stuff. It might be a promininent candidate other platforms adopt. >> >> my two cents, >> >> Norbert >> >> >> >

April 16, 2011

[Pharo-project] [update 1.3] #13159

by Marcus Denker

13159 ----- Issue 4031: Remove Mail to list in ChangeSorter Issue 4030: defaultBackgroundColor should not use self theme Issue 3872: [Failing Test] 1.3 HttpUrlTest.testHttps Issue 3598: [Failing Test]Tests.Compiler.CompilerTest.testNotInteractiveInBlockTempArgumentShadowing Issue 3981: #<= on SourcedMethodReference is very slow -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 16, 2011