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

Re: [Pharo-project] [Progress Report] Zinc HTTP Components

by Sven Van Caekenberghe

On 14 Nov 2011, at 07:18, Sven Van Caekenberghe wrote: > On 13 Nov 2011, at 23:59, StÃ©phane Ducasse wrote: > >> do you know if we should merge with the latest version in 1.4? > > Yes we should, the code is in a good state. > I will make an issue because we should record the exact version that got integrated. I 'reopened' http://code.google.com/p/pharo/issues/detail?id=4903

Nov. 14, 2011

Re: [Pharo-project] gsub like solution for Pharo/Smalltalk

by Sven Van Caekenberghe

On 14 Nov 2011, at 08:25, mail list wrote: > I have a dictionary of keys and values. > > I have a text string in which the keys are marked with before and ending symbols. > > In ruby to replace the key with the value in the text string is reasonably simple. (eg Dictionary.each { key,value | string.gsub!(key,value) } - or similar to this. > > While I don't mind rolling my version of this in Smalltalk, just exploring the regex code and the streams code it is not obvious where is the easiest place to start. > > If someone would put their comments on where to start I will build the functionality and put it up on squeaksource since I think it is common requirement. > > S. There is String>>#format: but there are probably other options as well. Sven

Nov. 14, 2011

[Pharo-project] gsub like solution for Pharo/Smalltalk

by mail list

I have a dictionary of keys and values. I have a text string in which the keys are marked with before and ending symbols. In ruby to replace the key with the value in the text string is reasonably simple. (eg Dictionary.each { key,value | string.gsub!(key,value) } - or similar to this. While I don't mind rolling my version of this in Smalltalk, just exploring the regex code and the streams code it is not obvious where is the easiest place to start. If someone would put their comments on where to start I will build the functionality and put it up on squeaksource since I think it is common requirement. S.

Nov. 14, 2011

Re: [Pharo-project] [Progress Report] Zinc HTTP Components

by Sven Van Caekenberghe

On 14 Nov 2011, at 02:00, mail list wrote: > I have been very happily using ZNNeoClient. That is good to hear. > Does this mean that ZNClient is now the replacement for ZNNeoClient? Yes, indeed. ZnNeoClient was the 'working title'. Regards, Sven

Nov. 14, 2011

Re: [Pharo-project] [Progress Report] Zinc HTTP Components

by Sven Van Caekenberghe

On 13 Nov 2011, at 23:59, StÃ©phane Ducasse wrote: > do you know if we should merge with the latest version in 1.4? Yes we should, the code is in a good state. I will make an issue because we should record the exact version that got integrated. Sven

Nov. 14, 2011

Re: [Pharo-project] Sexy font look

by HwaJong Oh

Can you give me some more detailed directions? I really want this! :-) -- View this message in context: http://forum.world.st/Sexy-font-look-tp3874250p4038534.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 14, 2011

Re: [Pharo-project] Broken #isPrime

by David T. Lewis

I think this may be just an incomplete update from Squeak trunk. I added a comment to the issue to explain. Dave On Sun, Nov 13, 2011 at 06:21:50PM +0100, St?phane Ducasse wrote: > Thanks dave > > http://code.google.com/p/pharo/issues/detail?id=4997 > > Stef > > On Nov 13, 2011, at 4:58 PM, David T. Lewis wrote: > > > Hi, > > > > There seems to be a problem with #isPrime in Pharo 1.4. The following example > > runs apparently forever: > > > > 100000000000000000000000000039 isPrime. > > > > Unfortunately I used #isPrime to demonstrate multiprocessing with worker > > images with RemoteTask. RemoteTask seems to work fine on Pharo, but the > > examples run "forever" and thus appear to fail due to the #isPrime problem. > > > > RemoteTask is described here > > <http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-November/162167…> > > > > > > Dave >

Nov. 14, 2011

Re: [Pharo-project] [Progress Report] Zinc HTTP Components

by mail list

I have been very happily using ZNNeoClient. Does this mean that ZNClient is now the replacement for ZNNeoClient? Thanks S. On Nov 14, 2011, at 5:56 AM, Sven Van Caekenberghe wrote: > Hi, > > This is a list of the most important changes to Zn since May 1st 2011: > > - added brand new ZnClient to replace all other HTTP clients (who became deprecated) > this is an object to build, execute and process HTTP client requests, > it has a rich protocol to construct requests and to access responses, > it has various error handling options, > it can reuse an existing connection to a specific host:port, > it can handle sessions, cookies, redirects and authentication, > it has many options (settings) with sensible defaults. > here is the simplest example: > ZnClient new > get: 'http://zn.stfx.eu/zn/numbers.txt' > and here is an example using some features to make a better HTTP request: > ZnClient new > systemPolicy; > accept: ZnMimeType textPlain; > http; > host: 'zn.stfx.eu'; > path: 'zn/numbers.txt'; > contentReader: [ :entity | entity contents lines collect: [ :each | each asNumber ] ]; > ifFail: [ :exception | self inform: 'I am sorry: ', exception printString ]; > get > - added support so that HTTPS works out of the box if Zodiac is present. > this should work when Zodiac is loaded and the necessary plugin is present: > ZnClient new > url: 'https://www.google.com/search'; > queryAt: 'q' put: 'Pharo Smalltalk'; > get > - added a new subclass, ZnManagingMultiThreadedServer, that keeps track of open > worker connections so that they can be properly closed when needed. > to use this server with the Zn Seaside adaptor, you can do this: > ZnZincServerAdaptor new > port: 8080; > serverClass: ZnManagingMultiThreadedServer; > start > - refactored ZnNetworkingUtils, it is now (also) a factory for creating socket streams > - added ZnDispatcherDelegate for straight-forward dispatching to mapped urls (thx Nick Ager) > - cleanup of the cookie handling API > - fixed support for HTTP proxies (thx Alexandre Bergel for reporting) > - localhost URLs are now excluded from being proxied > - working around SocketStream>>#atEnd issues by using #peek > - implemented support for proxies that require authorization > - introduced ZnConnectionTimeout process variable > - added ManagedServers class variable to ZnServer to dispatch the system's > #startUp/#shutDown messages to all server instances that are #register-ed > - implemented client side support for If-Modified-Since and Not Modified > - changed ZnMimePart>>#fieldValueString to return an empty string instead of 'nil' > when the field is empty or absent (Thx Lukas Renggli) > - added support for dealing with certain defaults in ZnUrl > - added code to throw a ZnMissingHost exception when a bogus ZnUrl is used to connect to a HTTP host > - added ZnMimeType wildcard constants #any and #text > - added ZnHttpUnsuccessful and ZnUnexpectedContentType exceptions > - added a nice example to ZnEasy class>>#getPng: (Thx Lukas Renggli) > - added ZnUtils class>>#parseHttpDate: for use in ZnCookie>>#expiresTimeStamp > - added optional delegate #close-ing to ZnServer hierarchy > - added some Pharo 1.2 compatibility (ZnMultiThreadedServer>>#exceptionSet:) > - lots of small fixes, cleanup and improved documentation > > Sven > >

Nov. 14, 2011

Re: [Pharo-project] [Progress Report] Zinc HTTP Components

by StÃ©phane Ducasse

thanks sven do you know if we should merge with the latest version in 1.4? Stef On Nov 13, 2011, at 10:56 PM, Sven Van Caekenberghe wrote: > Hi, > > This is a list of the most important changes to Zn since May 1st 2011: > > - added brand new ZnClient to replace all other HTTP clients (who became deprecated) > this is an object to build, execute and process HTTP client requests, > it has a rich protocol to construct requests and to access responses, > it has various error handling options, > it can reuse an existing connection to a specific host:port, > it can handle sessions, cookies, redirects and authentication, > it has many options (settings) with sensible defaults. > here is the simplest example: > ZnClient new > get: 'http://zn.stfx.eu/zn/numbers.txt' > and here is an example using some features to make a better HTTP request: > ZnClient new > systemPolicy; > accept: ZnMimeType textPlain; > http; > host: 'zn.stfx.eu'; > path: 'zn/numbers.txt'; > contentReader: [ :entity | entity contents lines collect: [ :each | each asNumber ] ]; > ifFail: [ :exception | self inform: 'I am sorry: ', exception printString ]; > get > - added support so that HTTPS works out of the box if Zodiac is present. > this should work when Zodiac is loaded and the necessary plugin is present: > ZnClient new > url: 'https://www.google.com/search'; > queryAt: 'q' put: 'Pharo Smalltalk'; > get > - added a new subclass, ZnManagingMultiThreadedServer, that keeps track of open > worker connections so that they can be properly closed when needed. > to use this server with the Zn Seaside adaptor, you can do this: > ZnZincServerAdaptor new > port: 8080; > serverClass: ZnManagingMultiThreadedServer; > start > - refactored ZnNetworkingUtils, it is now (also) a factory for creating socket streams > - added ZnDispatcherDelegate for straight-forward dispatching to mapped urls (thx Nick Ager) > - cleanup of the cookie handling API > - fixed support for HTTP proxies (thx Alexandre Bergel for reporting) > - localhost URLs are now excluded from being proxied > - working around SocketStream>>#atEnd issues by using #peek > - implemented support for proxies that require authorization > - introduced ZnConnectionTimeout process variable > - added ManagedServers class variable to ZnServer to dispatch the system's > #startUp/#shutDown messages to all server instances that are #register-ed > - implemented client side support for If-Modified-Since and Not Modified > - changed ZnMimePart>>#fieldValueString to return an empty string instead of 'nil' > when the field is empty or absent (Thx Lukas Renggli) > - added support for dealing with certain defaults in ZnUrl > - added code to throw a ZnMissingHost exception when a bogus ZnUrl is used to connect to a HTTP host > - added ZnMimeType wildcard constants #any and #text > - added ZnHttpUnsuccessful and ZnUnexpectedContentType exceptions > - added a nice example to ZnEasy class>>#getPng: (Thx Lukas Renggli) > - added ZnUtils class>>#parseHttpDate: for use in ZnCookie>>#expiresTimeStamp > - added optional delegate #close-ing to ZnServer hierarchy > - added some Pharo 1.2 compatibility (ZnMultiThreadedServer>>#exceptionSet:) > - lots of small fixes, cleanup and improved documentation > > Sven > >

Nov. 13, 2011

[Pharo-project] [Progress Report] Zinc HTTP Components

by Sven Van Caekenberghe

Hi, This is a list of the most important changes to Zn since May 1st 2011: - added brand new ZnClient to replace all other HTTP clients (who became deprecated) this is an object to build, execute and process HTTP client requests, it has a rich protocol to construct requests and to access responses, it has various error handling options, it can reuse an existing connection to a specific host:port, it can handle sessions, cookies, redirects and authentication, it has many options (settings) with sensible defaults. here is the simplest example: ZnClient new get: 'http://zn.stfx.eu/zn/numbers.txt' and here is an example using some features to make a better HTTP request: ZnClient new systemPolicy; accept: ZnMimeType textPlain; http; host: 'zn.stfx.eu'; path: 'zn/numbers.txt'; contentReader: [ :entity | entity contents lines collect: [ :each | each asNumber ] ]; ifFail: [ :exception | self inform: 'I am sorry: ', exception printString ]; get - added support so that HTTPS works out of the box if Zodiac is present. this should work when Zodiac is loaded and the necessary plugin is present: ZnClient new url: 'https://www.google.com/search'; queryAt: 'q' put: 'Pharo Smalltalk'; get - added a new subclass, ZnManagingMultiThreadedServer, that keeps track of open worker connections so that they can be properly closed when needed. to use this server with the Zn Seaside adaptor, you can do this: ZnZincServerAdaptor new port: 8080; serverClass: ZnManagingMultiThreadedServer; start - refactored ZnNetworkingUtils, it is now (also) a factory for creating socket streams - added ZnDispatcherDelegate for straight-forward dispatching to mapped urls (thx Nick Ager) - cleanup of the cookie handling API - fixed support for HTTP proxies (thx Alexandre Bergel for reporting) - localhost URLs are now excluded from being proxied - working around SocketStream>>#atEnd issues by using #peek - implemented support for proxies that require authorization - introduced ZnConnectionTimeout process variable - added ManagedServers class variable to ZnServer to dispatch the system's #startUp/#shutDown messages to all server instances that are #register-ed - implemented client side support for If-Modified-Since and Not Modified - changed ZnMimePart>>#fieldValueString to return an empty string instead of 'nil' when the field is empty or absent (Thx Lukas Renggli) - added support for dealing with certain defaults in ZnUrl - added code to throw a ZnMissingHost exception when a bogus ZnUrl is used to connect to a HTTP host - added ZnMimeType wildcard constants #any and #text - added ZnHttpUnsuccessful and ZnUnexpectedContentType exceptions - added a nice example to ZnEasy class>>#getPng: (Thx Lukas Renggli) - added ZnUtils class>>#parseHttpDate: for use in ZnCookie>>#expiresTimeStamp - added optional delegate #close-ing to ZnServer hierarchy - added some Pharo 1.2 compatibility (ZnMultiThreadedServer>>#exceptionSet:) - lots of small fixes, cleanup and improved documentation Sven

Nov. 13, 2011