[Pharo-project] [update 2.0] #20514 (Zinc Update)
Issue 7375: Zinc Update January 2013 http://code.google.com/p/pharo/issues/detail?id=7375 Sven explains: Since http://code.google.com/p/pharo/issues/detail?id=7180 there were the following changes: - support for server routes (session affinity, sticky sessions) - new API to access the server URL (#url, #serverUrl, #scheme) - ZnResponse class>>#redirect: and #created: now accept absolute URLs as well (thx Jan van de Sandt) - New ZnRequest API (all suggested by Jan van de Sandt): #host to return the Host: header field as ZnUrl #relativeUrl to explicitely request the request line uri as a relative URL #absoluteUrl to combine the request line URL with the host URL into an absolute URL #mergedFields to return a multi value dictionary combining query fields and application url encoded form fields - ZnClient>>#redirectUrl now uses ZnUrl>>#inContextOf: - Reimplemented ZnApplicationUrlEncodedEntity>>#addAll: and ZnHeaders>>#addAll: using ZnMultiValueDictionary>>#addAllMulti: - fix ZnUtils class>>#signalProgress:total: bug when total was nil: #format: index should be 1 not 0 (Thx Camillo Bruni !) - added ZnMessage>>#writeToTranscript - Bugfix to ZnApplicationFormUrlEncodedEntity>>#readFrom: which failed when content-length was not specified (Thx Jan van de Sandt) - Extended ZnClient>>#url: to accept the new user info (username and password) component of ZnUrl when present - ZnRequestLine>>#uri: now explicitely calls #enforceKnownScheme - various refactorings, cleanups - moved ZnMonticelloServerDelegate from Zinc-HTTP-Client-Server to Zinc-FileSystem and Zinc-FileSystem-Legacy - ZnServer's #handleRequestProtected: will now also do a #logServerError unless #logServerDetails is false - this gives exception, signaller context details and a stack trace of depth 8 when an unhandled error occurs - There is also a new package, Zinc-Resource-Meta-FileSystem, containing bidirectional conversions between ZnUrl and FileReference using #asZnUrl and #asFileReference.
No, it does not work I have no clue why not, I could load it just now when filing in directly the update file, but when I do load update it does not find the file on the server. On Feb 5, 2013, at 1:52 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
Issue 7375: Zinc Update January 2013 http://code.google.com/p/pharo/issues/detail?id=7375
Sven explains:
Since http://code.google.com/p/pharo/issues/detail?id=7180 there were the following changes:
- support for server routes (session affinity, sticky sessions) - new API to access the server URL (#url, #serverUrl, #scheme) - ZnResponse class>>#redirect: and #created: now accept absolute URLs as well (thx Jan van de Sandt) - New ZnRequest API (all suggested by Jan van de Sandt): #host to return the Host: header field as ZnUrl #relativeUrl to explicitely request the request line uri as a relative URL #absoluteUrl to combine the request line URL with the host URL into an absolute URL #mergedFields to return a multi value dictionary combining query fields and application url encoded form fields - ZnClient>>#redirectUrl now uses ZnUrl>>#inContextOf: - Reimplemented ZnApplicationUrlEncodedEntity>>#addAll: and ZnHeaders>>#addAll: using ZnMultiValueDictionary>>#addAllMulti: - fix ZnUtils class>>#signalProgress:total: bug when total was nil: #format: index should be 1 not 0 (Thx Camillo Bruni !) - added ZnMessage>>#writeToTranscript - Bugfix to ZnApplicationFormUrlEncodedEntity>>#readFrom: which failed when content-length was not specified (Thx Jan van de Sandt) - Extended ZnClient>>#url: to accept the new user info (username and password) component of ZnUrl when present - ZnRequestLine>>#uri: now explicitely calls #enforceKnownScheme - various refactorings, cleanups - moved ZnMonticelloServerDelegate from Zinc-HTTP-Client-Server to Zinc-FileSystem and Zinc-FileSystem-Legacy - ZnServer's #handleRequestProtected: will now also do a #logServerError unless #logServerDetails is false - this gives exception, signaller context details and a stack trace of depth 8 when an unhandled error occurs - There is also a new package, Zinc-Resource-Meta-FileSystem, containing bidirectional conversions between ZnUrl and FileReference using #asZnUrl and #asFileReference.
On Feb 5, 2013, at 1:59 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 05 Feb 2013, at 13:55, Marcus Denker <marcus.denker@inria.fr> wrote:
but when I do load update it does not find the file on the server.
You mean that one of the versions in not in the inbox ?
No, it gets an error and claims that they are not there yet they are. Marcus
On Feb 5, 2013, at 2:12 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Feb 5, 2013, at 1:59 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 05 Feb 2013, at 13:55, Marcus Denker <marcus.denker@inria.fr> wrote:
but when I do load update it does not find the file on the server.
You mean that one of the versions in not in the inbox ?
No, it gets an error and claims that they are not there yet they are.
You can try it yourself, I added it to the tracker entry. Sadly I spend already >30 minutes on this and I should do something else. Marcus
The 20514-Pha-Zinc.cssays you are loading from http://ss3.gemstone.com/ss/Pharo20 yet for example Zinc-Character-Encoding-Core-SvenVanCaekenberghe.5.mcz is not there as are none of the other versions, either the .cs is loading from the wrong repository or they were not (yet) copied or maybe I misunderstand and does the copying happen automatically before that ? On 05 Feb 2013, at 14:11, Marcus Denker <marcus.denker@inria.fr> wrote:
On Feb 5, 2013, at 1:59 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 05 Feb 2013, at 13:55, Marcus Denker <marcus.denker@inria.fr> wrote
but when I do load update it does not find the file on the server.
You mean that one of the versions in not in the inbox ?
No, it gets an error and claims that they are not there yet they are.
Marcus
On Feb 5, 2013, at 2:23 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
The 20514-Pha-Zinc.cssays you are loading from http://ss3.gemstone.com/ss/Pharo20 yet for example Zinc-Character-Encoding-Core-SvenVanCaekenberghe.5.mcz is not there as are none of the other versions, either the .cs is loading from the wrong repository or they were not (yet) copied or maybe I misunderstand and does the copying happen automatically before that ?
ups. that's it! I was then looking at them, which copied them into my cache and the script worked because of that locally :-) I will copy them, then it will work. Marcus
On 05 Feb 2013, at 14:11, Marcus Denker <marcus.denker@inria.fr> wrote:
On Feb 5, 2013, at 1:59 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 05 Feb 2013, at 13:55, Marcus Denker <marcus.denker@inria.fr> wrote
but when I do load update it does not find the file on the server.
You mean that one of the versions in not in the inbox ?
No, it gets an error and claims that they are not there yet they are.
Marcus
On 05 Feb 2013, at 14:26, Marcus Denker <marcus.denker@inria.fr> wrote:
On Feb 5, 2013, at 2:23 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
The 20514-Pha-Zinc.cssays you are loading from http://ss3.gemstone.com/ss/Pharo20 yet for example Zinc-Character-Encoding-Core-SvenVanCaekenberghe.5.mcz is not there as are none of the other versions, either the .cs is loading from the wrong repository or they were not (yet) copied or maybe I misunderstand and does the copying happen automatically before that ?
ups. that's it!
I was then looking at them, which copied them into my cache and the script worked because of that locally :-)
I will copy them, then it will work.
Let's hope so ;-)
Marcus
On 05 Feb 2013, at 14:11, Marcus Denker <marcus.denker@inria.fr> wrote:
On Feb 5, 2013, at 1:59 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 05 Feb 2013, at 13:55, Marcus Denker <marcus.denker@inria.fr> wrote
but when I do load update it does not find the file on the server.
You mean that one of the versions in not in the inbox ?
No, it gets an error and claims that they are not there yet they are.
Marcus
I ***love*** such kind of mail :) Stef On Feb 5, 2013, at 1:51 PM, Marcus Denker wrote:
Issue 7375: Zinc Update January 2013 http://code.google.com/p/pharo/issues/detail?id=7375
Sven explains:
Since http://code.google.com/p/pharo/issues/detail?id=7180 there were the following changes:
- support for server routes (session affinity, sticky sessions) - new API to access the server URL (#url, #serverUrl, #scheme) - ZnResponse class>>#redirect: and #created: now accept absolute URLs as well (thx Jan van de Sandt) - New ZnRequest API (all suggested by Jan van de Sandt): #host to return the Host: header field as ZnUrl #relativeUrl to explicitely request the request line uri as a relative URL #absoluteUrl to combine the request line URL with the host URL into an absolute URL #mergedFields to return a multi value dictionary combining query fields and application url encoded form fields - ZnClient>>#redirectUrl now uses ZnUrl>>#inContextOf: - Reimplemented ZnApplicationUrlEncodedEntity>>#addAll: and ZnHeaders>>#addAll: using ZnMultiValueDictionary>>#addAllMulti: - fix ZnUtils class>>#signalProgress:total: bug when total was nil: #format: index should be 1 not 0 (Thx Camillo Bruni !) - added ZnMessage>>#writeToTranscript - Bugfix to ZnApplicationFormUrlEncodedEntity>>#readFrom: which failed when content-length was not specified (Thx Jan van de Sandt) - Extended ZnClient>>#url: to accept the new user info (username and password) component of ZnUrl when present - ZnRequestLine>>#uri: now explicitely calls #enforceKnownScheme - various refactorings, cleanups - moved ZnMonticelloServerDelegate from Zinc-HTTP-Client-Server to Zinc-FileSystem and Zinc-FileSystem-Legacy - ZnServer's #handleRequestProtected: will now also do a #logServerError unless #logServerDetails is false - this gives exception, signaller context details and a stack trace of depth 8 when an unhandled error occurs - There is also a new package, Zinc-Resource-Meta-FileSystem, containing bidirectional conversions between ZnUrl and FileReference using #asZnUrl and #asFileReference.
participants (3)
-
Marcus Denker -
Stéphane Ducasse -
Sven Van Caekenberghe