October 2013 - Pharo-users - lists.pharo.org

Comanche in Pharo 2.0

by HernÃ¡n Morales Durand

Hello I want to update the KomHttpServer package in SmalltalkHub. It is just one method in ModDoc>>initialize which is now preventing to load KomHttpServer in Pharo 2.0. Is the Comanche in Seaside maintained? http://www.smalltalkhub.com/#!/~Seaside/KomHttpServer If not I will create a repository for Comanche. Cheers, HernÃ¡n

Oct. 21, 2013

create windows with Pharo 2.0

by Paolo Piccinelli

Good evening guys! I've some questions about creating a window in Pharo. I'd like to do a program usable through windows, so i need some advice about how to create a window with some textField and buttons to submit what i write into the fields. Is it correct to use the StandardWindow? Is there something else that i need to know? Thanks in Advance!Best;Paolo

Oct. 21, 2013

Zodiac/SqueakSSL plugin on OSX with Pharo 2.0 error

by recursive68＠gmail.com

>Yes, this is a known issue: certificate management is simple not implemented in the plugin. Client side you >can ignore this (although that is a security problem), server side it is functionally necessary. > >ZnSecureServer only works on Linux, AFAIK. I've said this from day one. > >Sven Thanks for the info.

Oct. 20, 2013

Re: [Pharo-users] Monticello and HTTPS

by Manfred KrÃ¶hnert

Hello Sven, thank you very much again for your help and sorry for the late reply. Up to now I didn't have a chance to check back on this issue. On Mon, Oct 14, 2013 at 11:49 AM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > Hi Manfred, > > On 13 Oct 2013, at 23:56, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> > wrote: > > > Hello Sven, > > > > I had some time to look further into this issue. > > > > On Thu, Oct 10, 2013 at 9:08 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > Manfred, > > > > On 10 Oct 2013, at 20:17, Manfred KrÃ¶hnert <mkroehnert42(a)googlemail.com> > wrote: > > > > > Hi again, > > > > > > the webdav share is located on an OwnCloud instance. > > > It is possible to get a directory listing of the specific directory > with the following ZnClient request: > > > > > > ZnClient new username: 'X' password: 'Y'; get: ' > https://owncloud.server.de/remote.php/webdav/monticello' > > > > Excellent, that means that it fundamentally works ! > > > > Maybe you can try the same for accessing an actual .mcz file, just to be > sure. > > > > If I add a '/MyPackage-MK.1.mcz' to the URL and inspect the result it > shows a big ByteArray instance. > > Which should mean that the file can get accessed remotely via WebDAV. > > Great: so this means that there is no fundamental problem at the HTTP or > Zn level. > > > > In a Pharo 2.0 image do the following steps: > > > > > > * MonticelloBrowser: select package > > > * MonticelloBrowser->'+Repository' > > > * add location: ' > https://owncloud.server.de/remote.php/webdav/monticello' username: 'X' > password: 'Y' > > > * MonticelloBrowser->'Open' > > > > > > * ProgressBar with the following name shows up: > > > 'Loading all file names from > https://owncloud.server.de/remote.php/webdav/monticello' > > > It gets interrupted by a PreDebugWindow with title > > > 'MCRepositoryError: Could not access > https://owncloud.server.de/remote.php/webdav/monticello: > ZnHttpUnsuccessful: 404 Not Found' > > > > > > Opening the Debugger gives the following stacktrace > > > > > > MCHttpRepository>>loadAllFileNames in Block: [:exception | (exception > className beginsWith: 'Zn...etc... > > > BlockClosure>>cull: > > > ... > > > ZnClient>>execute > > > > Have a look at MCHTTPRepository>>#loadAllFileNames and notice how a > query parameter is added, maybe that is the culprit ? Also, a trailing > slash is added, that could be a problem for the server as well. > > > > What I found out is that line 11 of MCHTTPRepository>>#loadAllFileNames > is apparently causing the problem: > > > > queryAt: 'C' put: 'M;O=D'; "legacy that some servers maybe expect" > > > > > > When I access the following URL with ZnClient it returns a 404 error > (does not exist): > > > > ZnClient new username: 'X' password: 'Y'; get: ' > https://owncloud.server.de/remote.php/webdav/monticello/?C=M%3BO%3DD' > > > > This 404 is the exception which is thrown and caught by the debugger. > > I took the query from the http client request which I inspected in the > debugger. > > > > When the 'queryAt:...' line is commented out the contents of the > repository is shown when I choose 'Open' on the specific repository in > MonticelloBrowser. > > Maybe this is an issue with the WebDAV implementation of OwnCloud > (version 5.0.10 in this case). > > Like the comment says: this is something weird from the past, I do not > know what it means. Maybe the time has come to just remove it. Yes, this could be the case. But I wont vote for it since I don't have any experience in this area ;-) > > The next strange thing here is that all entries in the opened browser > are prefixed with 'remote.php/webdav/monticello/'. > > And they are all marked in a bold font which means completely new to the > system if I remember correctly. > > Then I checked the MD5 sums of the .mcz files and the ones from the > package cache have a different checksum than the one on the webdav share. > > Although I used the MonticelloBrowser 'Copy' action. > > The repository listing has to be correct, also in its use of naming and > URLs. This is a correct one: http://mc.stfx.eu/ZincHTTPComponents/ - note > the simple name and relative URL. But such a relative URL can only work if > the base URL of the page ends with /. Monticello can work on WebDAV but it is not written specifically for it. > Maybe there are others out there who can help you better how to configure > your server. > > You could also have a look at ZnMonticelloServerDelegate, which is an > implementation of a very simple Monticello repository server in Pharo. You > should be able to understand the simple protocol from that code. > I see. The listing I get from the OwnCloud server looks a bit different. More like a general Directory listing with additional information like size, type, and modification date arranged in a table. It might be that the complete path behind the server domain is used in my case and not stripped down to the last part of the URL. If I get a chance to do so I'll check this myself. No need for you to dive in. For now I found a different way to synchronize my packages without this server. Best, Manfred

Oct. 20, 2013

Re: [Pharo-users] Zodiac/SqueakSSL plugin on OSX with Pharo 2.0 error

by Sven Van Caekenberghe

Yes, this is a known issue: certificate management is simple not implemented in the plugin. Client side you can ignore this (although that is a security problem), server side it is functionally necessary. ZnSecureServer only works on Linux, AFAIK. I've said this from day one. Sven On 20 Oct 2013, at 14:00, recursive68(a)gmail.com wrote: > Forgot to include command that fails: > > (ZnSecureServer on: 8443 ) > certificate: '/Development/Smalltalk/self-crt/server.pem'; > logToTranscript; > start; > yourself. >

Oct. 20, 2013

Zodiac/SqueakSSL plugin on OSX with Pharo 2.0 error

by recursive68＠gmail.com

Forgot to include command that fails: (ZnSecureServer on: 8443 ) certificate: '/Development/Smalltalk/self-crt/server.pem'; logToTranscript; start; yourself.

Oct. 20, 2013

Zodiac/SqueakSSL plugin on OSX with Pharo 2.0 error

by recursive68＠gmail.com

Hi, I'm getting this plugin error when trying to use this command to run a SSL webserver on OSX with Pharo 2.0/Zodiac/SqueakSSL plugin: Error: SSL Exception: accept failed [code: -5] being called here: accept "Do the SSL server handshake." | count result | self resetEncryptedBuffers. count := 0. connecting := true. [ self sslSession isConnected ] whileFalse: [ count := self readEncryptedBytes: in startingAt: 1 count: in size. result := self sslSession accept: in from: 1 to: count into: out. result < -1 ifTrue: [ ^ self sslException: 'accept failed' code: result ]. result > 0 ifTrue: [ self flushEncryptedBytes: out startingAt: 1 count: result ] ]. connecting := false Looking at the SqueakSSL plugin source code: -5 indicates a generic SSL exception/error, any ideas what this could be ? My self-signed certificate works fine when run using openssl ( openssl s_server -accept 8443 -cert server.pem -WWW ). Thanks

Oct. 20, 2013

Re: [Pharo-users] Alert Messages don't disappear

by Davide Varvello

Yep, I'd love to know why :-) Anyway, today there is no more that weird behaviour. I'm puzzled. Davide btc wrote > Do you mean you want to know why ? > Not within my capabilities. > > Do you just want them gone so you can continue working in the image? > Bring up halos on them and click > <Close> > . Exact key combinations varies > with OS platform. On windows its > <Alt-Shift-Click> > . > > cheers -ben -- View this message in context: http://forum.world.st/Alert-Messages-don-t-disappear-tp4715828p4715931.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 19, 2013

Re: [Pharo-users] ZnServer + keep alive

by Sven Van Caekenberghe

Hi Paul, On 19 Oct 2013, at 17:31, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > From reading the Zinc docs here: http://zn.stfx.eu/zn/zinc-http-components-paper.html I can see that ZnClient supports the 'Keep Alive' header. > > > Does ZnManagingMultiThreadedServer? > > > Seems like it does from the code, assuming the presence of the 'Keep-Alive' header from the client and a HTTP v 1.1 connection, but I'm not sure. Yes, both the old(er) HTTP 1.0 Keep-Alive behaviour as well as the current HTTP 1.1 behaviour (which keeps connections open by default) is implemented by both ZnClient and ZnMultiThreadServer and subclasses. > If so, is there a way to configure the timeout or max # of connections? I just want to make sure the settings in my nginx proxy match up with Zinc Currently, the server is lazy in the sense that it keeps connections open forever, or more precisely until they fail. Normally, a server should indeed protect itself by using both a limit on the number of connection that can be active concurrently and a specific timeout for closing kept alive connections. The max number of connection could be easily added, probably in ZnManagingMultiThreadedServer>>#socketStreamOn: where a 503 could then be returned. The hook for the other behaviour could be implemented by extending/overriding ZnManagingMultiThreadedServer>>#periodicTasks. The problem is of course that one thread/process would kill the connection of another, which could be in any state. Of course, putting nginx in front is a nice way to do resource protection in production. > Thanks > > Paul HTH, Sven

Oct. 19, 2013

ZnServer + keep alive

by Paul DeBruicker

From reading the Zinc docs here: http://zn.stfx.eu/zn/zinc-http-components-paper.html I can see that ZnClient supports the 'Keep Alive' header. Does ZnManagingMultiThreadedServer? Seems like it does from the code, assuming the presence of the 'Keep-Alive' header from the client and a HTTP v 1.1 connection, but I'm not sure. If so, is there a way to configure the timeout or max # of connections? I just want to make sure the settings in my nginx proxy match up with Zinc Thanks Paul

Oct. 19, 2013