January 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] singleton trait

by Siemen Baader

On Thu, Jan 19, 2017 at 11:33 AM, Cyril Ferlicot D. < cyril.ferlicot(a)gmail.com> wrote: > > You just need a class variable #UniqueInstance and those methods: > > current > "Can also be named #default or #instance" > ^ UniqueInstance > ifNil: [ UniqueInstance := self basicNew; initialize; > yourself ] > Wouldn't a class instance variable be better? I want new singletons for every subclass. http://rmod-pharo-mooc.lille.inria.fr/MOOC/Slides/Week3/C019-W3S03-Basic-Va… I would also have used super new, why BasicNew? But my wish to create subclasses seems to answer that already. Thanks for your find-grained example, Cyril! Siemen

Jan. 19, 2017

Re: [Pharo-users] [Deployement] Apache rewrite rules for Pharo

by Blondeau Vincent

Hi, That is what I done to configure the apache server with 2 servers (one running on 8181 and the other on 8080): <VirtualHost *> ProxyPreserveHost On ProxyRequests Off RewriteEngine On RewriteRule ^/<my service>/(.*)$ http://localhost:8181/< my service >/$1 [proxy] RewriteRule ^(.*)$ http://localhost:8080$1 [proxy,last] ErrorLog /var/log/httpd/testServerError.log CustomLog /var/log/httpd/testServerCustom.log combined </VirtualHost> Vincent > -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de > Sven Van Caekenberghe > EnvoyÃ© : mercredi 18 janvier 2017 19:49 > Ã : Any question about pharo is welcome > Objet : Re: [Pharo-users] [Deployement] Apache rewrite rules for Pharo > > There is also this chapter: > > https://ci.inria.fr/pharo- > contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book- > result/DeploymentWeb/DeployForProduction.html > > which contains the same solution and more. > > > On 18 Jan 2017, at 19:04, Steven Costiou <steven.costiou(a)kloum.io> > wrote: > > > > Hi, > > > > not sure that's what you are looking for but for my Pharo images with Iliad > applications i just add the following to my website vhost in the /etc/apache > directory: > > > > ProxyPass / http://localhost:7777/ > > ProxyPassReverse / http://localhost:7777/ > > > > That redirects all queries to my domain to this local url, for example > > http://my-domain.com/iliad => http://localhost:7777/iliad > > > > Works fine but i don't even know if its the right thing to do (security > blabla...). I'm interested if someone knows a simpler procedure. > > > > Steven. > > > > > > Le 2017-01-18 18:22, Blondeau Vincent a Ã©crit : > > > >> Hi, > >> I need to put on the same server and access through the port 80 several > Pharo images. > >> I know that it is possible to do it thanks to the apache rewrite rules to > redirect outside urls http://myserver:80/myservice to internal ones: > http://localhost:8080. > >> Did someone already make such a config and can share the xml of the > configuration file? > >> Thanks in advance, > >> Cheers, > >> Vincent Blondeau > >> > >> > >> > >> > >> > !!!******************************************************** > ********** > >> ******************* "Ce message et les piÃ¨ces jointes sont > >> confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut > Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce > message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le > dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la > responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de > ce message. Bien que les meilleurs efforts soient faits pour maintenir cette > transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã > cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage > rÃ©sultant d'un virus transmis. > >> > >> This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted.!!!" > > > > > !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Jan. 19, 2017

Re: [Pharo-users] [Seaside] Bad Request ZnEntityTooLarge

by Sven Van Caekenberghe

Hi Bernard, Your analysis is correct. Most Seaside adaptors, including ZnZincServerAdaptor, are implemented so that the incoming (Zn) request is read from the wire, then converted to Seaside WA* objects, processed, the result converted from WA* objects to an outgoing (Zn) response and put on the wire. Zn has some built-in resource protection measures, including a limit on how large entities (bodies) can be. The error of crossing such a limit is raised in the very first step, outside the scope of your Seaside handling code. At first sight, I would not immediately know how this can be solved. Note that in order to know how much is coming in, you have to read it, but you have to stop in time. Note also that the content-length header could be absent or wrong (a malicious request). I can't remember where we currently stand on a streaming Zn Seaside adaptor, there were some experiments in the past IIRC. That could be a solution, because then the entity/body is not read until further down the line, if we can get it to work. The current one only seems to do streaming for responses. Sven > On 19 Jan 2017, at 13:32, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > I have a Seaside application which includes a file upload feature. > > renderContentOn: html > â¦ > html fileUpload > callback: [ :file | self receiveFile: file ]. > html submitButton: 'Uploadâ ] > â¦ > > In receiveFile: I just save the uploaded file on the file system. > > When I upload a file larger than 16 MB an error page is shown with the error message: > Bad Request ZnEntityTooLarge > > I found that by using ZnConstants>>maximumEntitySize: I can increase this limit. However, I want to catch this in the image and show an error message to the user. > > I tried wrapping receiveFile: and renderContentOn: with an on:do: exception handler for ZnEntityTooLarge. However, neither works. It seems that the error happens before renderContentOn: is even called. I searched the mailing lists but did not come up with an answer. > > How can I achieve this in Seaside? Any help would be much appreciated. > > Cheers, > Bernhard > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Jan. 19, 2017

Bad Request ZnEntityTooLarge

by Bernhard Pieber

I have a Seaside application which includes a file upload feature. renderContentOn: html â¦ html fileUpload callback: [ :file | self receiveFile: file ]. html submitButton: 'Uploadâ ] â¦ In receiveFile: I just save the uploaded file on the file system. When I upload a file larger than 16 MB an error page is shown with the error message: Bad Request ZnEntityTooLarge I found that by using ZnConstants>>maximumEntitySize: I can increase this limit. However, I want to catch this in the image and show an error message to the user. I tried wrapping receiveFile: and renderContentOn: with an on:do: exception handler for ZnEntityTooLarge. However, neither works. It seems that the error happens before renderContentOn: is even called. I searched the mailing lists but did not come up with an answer. How can I achieve this in Seaside? Any help would be much appreciated. Cheers, Bernhard

Jan. 19, 2017

Re: [Pharo-users] singleton trait

by Siemen Baader

On Thu, Jan 19, 2017 at 11:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > The Traits would be cool to standardise the behaviour and to mark it as > such (implicit documentation) Exactly. > , however, Traits cannot add instance/class variables IIUC, that limits > what they can do (and would make it more than one step). > Ok. So that's the difference between a Ruby mixin and a trait. That's a shame, I think what Ruby does with mixins is really nice because it a) results in less code to test, and b) makes hineritance chains more semantic - you only inherit to model spcialization, not to reuse features. Cyril, many thanks! I know how to implement it and it is true that it is not much, but I had hoped to eliminate the code (and tests!) and use a standard feature if possible ;) -- Siemen > > > On 19 Jan 2017, at 11:33, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> > wrote: > > > > On 19/01/2017 11:23, Siemen Baader wrote: > >> Is there a trait to quickly create singletons in Pharo, along the way of > >> the Ruby Singleton mixin? > >> > >> https://ruby-doc.org/stdlib-1.9.3/libdoc/singleton/rdoc/Singleton.html > >> > >> (and ideally also observer/observable, which I am going to need next..) > >> > >> -- Siemen > > > > Hi! > > > > Singleton in Smalltalk are really easy so there is no Trait. > > > > You just need a class variable #UniqueInstance and those methods: > > > > current > > "Can also be named #default or #instance" > > ^ UniqueInstance > > ifNil: [ UniqueInstance := self basicNew; initialize; > yourself ] > > > > new > > ^ self error: 'I am a Singleton. Use current to get my instance or > > reset my instance with a new project. Maybe explain why there is a > > Singleton because we should avoid them if possible.' > > > > > > Now for the observer pattern you have the Announcement framework in > Pharo. > > > > I don't really have the time to explain but I think there is some doc on > > internet and on the help browser of Pharo. I found this: > > http://pharo.gemtalksystems.com/book/LanguageAndLibraries/announcements/ > > (I did not read it so I don't know what it's worth) > > > > -- > > Cyril Ferlicot > > > > http://www.synectique.eu > > > > 2 rue Jacques PrÃ©vert 01, > > 59650 Villeneuve d'ascq France > > > > >

Jan. 19, 2017

Re: [Pharo-users] singleton trait

by Denis Kudriashov

2017-01-19 11:37 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > The Traits would be cool to standardise the behaviour and to mark it as > such (implicit documentation), however, Traits cannot add instance/class > variables IIUC, that limits what they can do (and would make it more than > one step). > We could have statefull traits in future

Jan. 19, 2017

Re: [Pharo-users] singleton trait

by Sven Van Caekenberghe

The Traits would be cool to standardise the behaviour and to mark it as such (implicit documentation), however, Traits cannot add instance/class variables IIUC, that limits what they can do (and would make it more than one step). > On 19 Jan 2017, at 11:33, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 19/01/2017 11:23, Siemen Baader wrote: >> Is there a trait to quickly create singletons in Pharo, along the way of >> the Ruby Singleton mixin? >> >> https://ruby-doc.org/stdlib-1.9.3/libdoc/singleton/rdoc/Singleton.html >> >> (and ideally also observer/observable, which I am going to need next..) >> >> -- Siemen > > Hi! > > Singleton in Smalltalk are really easy so there is no Trait. > > You just need a class variable #UniqueInstance and those methods: > > current > "Can also be named #default or #instance" > ^ UniqueInstance > ifNil: [ UniqueInstance := self basicNew; initialize; yourself ] > > new > ^ self error: 'I am a Singleton. Use current to get my instance or > reset my instance with a new project. Maybe explain why there is a > Singleton because we should avoid them if possible.' > > > Now for the observer pattern you have the Announcement framework in Pharo. > > I don't really have the time to explain but I think there is some doc on > internet and on the help browser of Pharo. I found this: > http://pharo.gemtalksystems.com/book/LanguageAndLibraries/announcements/ > (I did not read it so I don't know what it's worth) > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Jan. 19, 2017

Re: [Pharo-users] singleton trait

by Cyril Ferlicot D.

On 19/01/2017 11:23, Siemen Baader wrote: > Is there a trait to quickly create singletons in Pharo, along the way of > the Ruby Singleton mixin? > > https://ruby-doc.org/stdlib-1.9.3/libdoc/singleton/rdoc/Singleton.html > > (and ideally also observer/observable, which I am going to need next..) > > -- Siemen Hi! Singleton in Smalltalk are really easy so there is no Trait. You just need a class variable #UniqueInstance and those methods: current "Can also be named #default or #instance" ^ UniqueInstance ifNil: [ UniqueInstance := self basicNew; initialize; yourself ] new ^ self error: 'I am a Singleton. Use current to get my instance or reset my instance with a new project. Maybe explain why there is a Singleton because we should avoid them if possible.' Now for the observer pattern you have the Announcement framework in Pharo. I don't really have the time to explain but I think there is some doc on internet and on the help browser of Pharo. I found this: http://pharo.gemtalksystems.com/book/LanguageAndLibraries/announcements/ (I did not read it so I don't know what it's worth) -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Jan. 19, 2017

singleton trait

by Siemen Baader

Is there a trait to quickly create singletons in Pharo, along the way of the Ruby Singleton mixin? https://ruby-doc.org/stdlib-1.9.3/libdoc/singleton/rdoc/Singleton.html (and ideally also observer/observable, which I am going to need next..) -- Siemen

Jan. 19, 2017

Re: [Pharo-users] STON encoding of slashes

by Peter Uhnak

On Wed, Jan 18, 2017 at 04:38:15PM +0100, Sven Van Caekenberghe wrote: > Being a superset means that you get a simple JSON parser (and even limited writer) for free once you install STON (or once it is part of the Pharo image, as it is now). It also means that we can fall back to the JSON spec as a guide in discussion like this one. It also helps people understand what STON is, by analogy but also differences with JSON. > > So my conclusion would be (while writing), always escape $\ and not $/, in pure STON mode (the default), escape $' and not $", in JSON mode, escape $" and not $'. Those would be the changes. Agreed ? > Yes for JSON, I guess yes for STON. (For me STON is effectively opaque representation (because of its DFS strategy), so I don't care too much about how it is stored (as long as it is not binary)) Thanks! Peter > > Peter > > > >>> On 18 Jan 2017, at 15:25, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >>> > >>> On Wed, Jan 18, 2017 at 11:11:06AM +0100, Christophe Demarey wrote: > >>>> > >>>>> Le 18 janv. 2017 Ã 09:51, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > >>>>> > >>>>> Hi Christophe, > >>>>> > >>>>>> STON toString: 'git@github.com:foo/bar.gitâ => ''git@github.com:foo\/bar.gitâ' > >>>>>> It used to be ''git@github.com:foo/bar.gitââ. > >>> > >>>>> In other words, it was an implementation error (omission). Note that JSON also has this escape. > >>> > >>> Yes and no for JSON. > >>> > >>> Only " and \ has to be escaped. Escaping anything else will give it special meaning with the exception of / which will just produce the same thing, because it is a special snowflake. :) > >>> > >>> quoted from https://tools.ietf.org/html/rfc7159#section-7: > >>> > >>> - Unicode characters may be placed within the quotation marks, except for the characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F). > >>> - Alternatively, there are two-character sequence escape representations of some popular characters. > >>> > >>> "/" (U+002F) doesn't fall into control character range, but the alternative section does permit it escaping it. > >>> > >>> In other words, JSON strings "\/", and "/", and "\u002f" are equivalent. > >>> > >>> But JSON itself doesn't require you to escape "/" (just like you are not required to escape "hi" into "\u0068\u0069", although you can). > >>> > >>> Note that other systems do not escape / by default: > >>> > >>> (Pharo) > >>> NeoJSONWriter toString: 'git@github.com:foo/bar.git' => "git@github.com:foo/bar.git" > >>> > >>> (JavaScript) > >>> JSON.stringify('git@github.com:foo/bar.git') => "git@github.com:foo/bar.git" > >>> > >>> (Ruby) > >>> require 'json' > >>> puts 'git@github.com:foo/bar.git'.to_json => "git@github.com:foo/bar.git" > >>> > >>> Peter > >>> > >> > >> > > > >

Jan. 19, 2017