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

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Sven Van Caekenberghe

On 28 Jul 2011, at 21:11, Lukas Renggli wrote: > I cannot reproduce, but one thing that seems strange with Zinc is that > when I stop the server it actually takes 10 to 20 seconds for the site > to stop responding ... :-/ > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch ZnMultiThreadedServer does not currently hold onto the list of workers and/or connections that is spawns. So when you kill it, the server socket is stopped, but I could imagine that a kept alive connection in a browser still works until the browser closes it. Let's call this a feature ;-) Sven

July 28, 2011

Re: [Pharo-project] [ANN] Customized Cog Win32 for Pharo 1.3 (based on Cog r2474)

by Esteban Lorenzano

ehhh... I was making a joke, not an actual point! you guys are too serious lately ;) On Thu, Jul 28, 2011 at 4:29 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > OK, thanks for the pointer to > https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog-Win32/ > > > Still this one is not yet customized to use the "lighthouse and gear" > icon. It also does not include a resource section - so one can find > out the vendor and version easily using explorer directly on the EXE's > properties. > > Any admin would be suspicious if he would find an EXE on a hard disk > that does not include the vendor and product name. This info is > also used when the firewall pops up as soon as you have a Seaside > app running that requests network access. With this (not yet branded) > VM the info would be empty... > > I can provide the necessary info/files for that, so we can include them > into the auto build. This is easy to change. > > > But still I dont know what the codebase of this auto build Cog VM > for windows is. Is it the Subversion repo from Eliot or the > Git clone from Igor? > > If it is the git one how does it relate to Eliots work, for instance > is the IAB32 and MT stuff already part of it as in #r2474? > Is it auto-merged or who is in charge of merging things into it? > > I know this could end up in a discussion about Pharo forking and > personal working styles - but nonetheless I'm eager to know more > about all these (now distributed?) work being done. > > Esteban wrote: > > let me guess... why can that be happening... oh, I know: you are using > > windows! > > Anything I can answer here is that Windows is one of the relevant > parts of the IT market - if we want Pharo to be successfull in > commercial environments we should help developers/pharo users to > easily feel comfortable in these environments and help their > customers on ANY platform - including Windows. So your comment > didnt help to make the situation better, did it? > > Nothing more to add. > > Thx > T. > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > >

July 28, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by StÃ©phane Ducasse

I know that with Sven we went over HTTPSocket or HTTPClient uses because some of them were crazy. Now I know that Chris muler found a bad behavior (pinging a server on failures) but we fixed that. I will go over the bug fixes to see if I see something. >> Excellent >> Let us know if you find problems because we can bullet profs Zn support for 1.3 > > Not sure what is going on with Swazoo and Kom. > > Swazoo doesn't work at all, but doesn't throw an error either (I don't > really care about that). > > Kom does work at startup, but manually starting it works. Stopping the > server takes about a minute though. This is kind of strange. Did > something with sockets change? > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

July 28, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Sven Van Caekenberghe

On 28 Jul 2011, at 20:54, Lukas Renggli wrote: > I don't think that the server manager calls #basicStop/#basicStart on > startup/shutdown (this is when you explicitly start/stop the server), > only #startUp/#shutDown. I might be wrong though ... Then why not implement #startUp/#shutDown by delegating to #basicStop/#basicStart Maybe Philippe knows the finer points. Sven

July 28, 2011

[Pharo-project] I love the idea of building to think

by StÃ©phane Ducasse

http://blog.flowingconcept.com/brandIt/on-design-thinking I think that this what we are doing when we build our research prototype and this is were Smalltalk is powerful. Tx sebastian for the link.

July 28, 2011

[Pharo-project] [ANN] Customized Cog Win32 for Pharo 1.3 (based on Cog r2474)

by Torsten Bergmann

OK, thanks for the pointer to https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog-Win32/ Still this one is not yet customized to use the "lighthouse and gear" icon. It also does not include a resource section - so one can find out the vendor and version easily using explorer directly on the EXE's properties. Any admin would be suspicious if he would find an EXE on a hard disk that does not include the vendor and product name. This info is also used when the firewall pops up as soon as you have a Seaside app running that requests network access. With this (not yet branded) VM the info would be empty... I can provide the necessary info/files for that, so we can include them into the auto build. This is easy to change. But still I dont know what the codebase of this auto build Cog VM for windows is. Is it the Subversion repo from Eliot or the Git clone from Igor? If it is the git one how does it relate to Eliots work, for instance is the IAB32 and MT stuff already part of it as in #r2474? Is it auto-merged or who is in charge of merging things into it? I know this could end up in a discussion about Pharo forking and personal working styles - but nonetheless I'm eager to know more about all these (now distributed?) work being done. Esteban wrote: > let me guess... why can that be happening... oh, I know: you are using > windows! Anything I can answer here is that Windows is one of the relevant parts of the IT market - if we want Pharo to be successfull in commercial environments we should help developers/pharo users to easily feel comfortable in these environments and help their customers on ANY platform - including Windows. So your comment didnt help to make the situation better, did it? Nothing more to add. Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

July 28, 2011

Re: [Pharo-project] Pharo Core HTTP Server OneCommandLine Demo

by StÃ©phane Ducasse

I like magic like that :) I want automation as much as possible. On Jul 28, 2011, at 9:16 PM, Sven Van Caekenberghe wrote: > How easy and how fast can you download, install and start an complete Pharo Core based HTTP Server on a bare Linux machine ? > > It just takes OneCommandLine: > > $ curl http://zn.stfx.eu/zn/pharo-server.sh | bash > > In well under a minute (in 11 seconds below, actually), you can browse http://localhost:1701 and all this with way less than 20Mb being downloaded. > > Mind you, this is quick hack, for some this will be old news, for others I hope this feels like magic. > > Some notes: > > - pharo-server.sh will download, install and start a Pharo Smalltalk HTTP server > - this script needs bash, curl, tar, unzip, at least, and was only tested on Ubuntu > - no special permissions needed, all files will reside in ~/pharo-server > - you will probably have to allow 1701 as a TCP port in your firewall for external access > - technically, the most interesting thing is the script called st-exec.sh > - you have to trust me that the installer is well-behaved, or have a look yourself ;-) > > Next is a terminal log of running this script, at the end there is a small benchmark showing what kind of performance you can expect from this setup (saving the best for last). The machine in question is an Amazon EC2 micro instance, the smallest, least powerful that you can get. > > Enjoy, > > Sven > > > $ curl http://zn.stfx.eu/zn/pharo-server.sh | bash > > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 1336 100 1336 0 0 53525 0 --:--:-- --:--:-- --:--:-- 652k > > pharo-server.sh will download, install and start a Pharo Smalltalk HTTP server > this script needs bash, curl, tar, unzip, at least, only tested on Ubuntu > no special permissions needed, all files will reside in /home/ubuntu/pharo-server > written by Sven Van Caekenberghe - http://stfx.eu > starting @ Thu Jul 28 18:50:12 UTC 2011 > creating work directory /home/ubuntu/pharo-server > downloading latest Pharo Core 1.3 > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 15.0M 100 15.0M 0 0 2408k 0 0:00:06 0:00:06 --:--:-- 2987k > extracting > Archive: pharo-core.zip > inflating: PharoCore-1.3/PharoCore-1.3.changes > inflating: PharoCore-1.3/PharoV10.sources > inflating: PharoCore-1.3/PharoCore-1.3.image > downloading a recent Cog VM > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 1524k 100 1524k 0 0 366k 0 0:00:04 0:00:04 --:--:-- 539k > extracting > downloading st-exec > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 2576 100 2576 0 0 99895 0 --:--:-- --:--:-- --:--:-- 1257k > creating startup script pharo-server.st > starting the server > Executing ./st-exec.sh pharo-server start PharoCore-1.3 > Working directory /home/ubuntu/pharo-server > Starting pharo-server in background > /home/ubuntu/pharo-server/coglinux/bin/squeak -vm-display-null -vm-sound-null /home/ubuntu/pharo-server/PharoCore-1.3.image /home/ubuntu/pharo-server/pharo-server.st > to stop the server execute > /home/ubuntu/pharo-server/st-exec.sh pharo-server stop PharoCore-1.3 > you can now access the server at > http://localhost:1701 > try > curl http://localhost:1701 > or > try > ab -k -n 1024 -c 8 http://localhost:1701/bytes > done @ Thu Jul 28 18:50:23 UTC 2011 > > > $ curl http://localhost:1701 > > <html> > <head> > <title>Zinc HTTP Components</title> > <style type="text/css"> > body { > color: black; > background: white; > width: 900px; > font-family: Verdana, Arial, Helvetica, sans-serif; > font-size: 13px; > } > p { > width: 600px; > padding: 0 20px 10px 20px; > } > ul,ol { > width: 600px; > padding: 0 5px 5px 30px; > } > #logo { > color: orange; > font-family: Helvetica, sans-serif; > font-weight: bold; > font-size: 100px; > } > </style> > </head> > <body> > <div id="logo">Zn</div> > <h1>Zinc HTTP Components</h1> > <p> > Welcome to Zinc HTTP Components, > a modern, open-source Smalltalk framework to deal with the HTTP networking protocol. > </p> > <ul> > <li>Project homepage <a href="http://homepage.mac.com/svc/Zinc-HTTP-Components/">http://homepage.mac.com/svc/Zinc-HTTP-Components/</a></li> > <li>SqueakSouce page <a href="http://www.squeaksource.com/ZincHTTPComponents.html">http://www.squeaksource.com/ZincHTTPComponents.html</a></li> > </ul> > <ul> > <li>Locally available pages <a href="/help">/help</a></li> > </ul> > <h4>May the Source be with you!</h4> > </body> > </html> > > > $ ab -k -n 1024 -c 8 http://localhost:1701/bytes > > This is ApacheBench, Version 2.3 <$Revision: 655654 $> > Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ > Licensed to The Apache Software Foundation, http://www.apache.org/ > > Benchmarking localhost (be patient) > Completed 102 requests > Completed 204 requests > Completed 306 requests > Completed 408 requests > Completed 510 requests > Completed 612 requests > Completed 714 requests > Completed 816 requests > Completed 918 requests > Completed 1020 requests > Finished 1024 requests > > > Server Software: Zinc > Server Hostname: localhost > Server Port: 1701 > > Document Path: /bytes > Document Length: 64 bytes > > Concurrency Level: 8 > Time taken for tests: 0.371 seconds > Complete requests: 1024 > Failed requests: 0 > Write errors: 0 > Keep-Alive requests: 1024 > Total transferred: 243712 bytes > HTML transferred: 65536 bytes > Requests per second: 2761.10 [#/sec] (mean) > Time per request: 2.897 [ms] (mean) > Time per request: 0.362 [ms] (mean, across all concurrent requests) > Transfer rate: 641.74 [Kbytes/sec] received > > Connection Times (ms) > min mean[+/-sd] median max > Connect: 0 0 0.2 0 4 > Processing: 0 3 29.8 0 365 > Waiting: 0 3 29.8 0 365 > Total: 0 3 29.8 0 367 > > Percentage of the requests served within a certain time (ms) > 50% 0 > 66% 0 > 75% 0 > 80% 0 > 90% 0 > 95% 0 > 98% 3 > 99% 5 > 100% 367 (longest request) > > > $ /home/ubuntu/pharo-server/st-exec.sh pharo-server pid PharoCore-1.3 > > Executing /home/ubuntu/pharo-server/st-exec.sh pharo-server pid PharoCore-1.3 > Working directory /home/ubuntu/pharo-server > 6289 > > > $ /home/ubuntu/pharo-server/st-exec.sh pharo-server stop PharoCore-1.3 > > Executing /home/ubuntu/pharo-server/st-exec.sh pharo-server stop PharoCore-1.3 > Working directory /home/ubuntu/pharo-server > Stopping pharo-server > Killing 6289 > > > $ /home/ubuntu/pharo-server/st-exec.sh pharo-server pid PharoCore-1.3 > Executing /home/ubuntu/pharo-server/st-exec.sh pharo-server pid PharoCore-1.3 > Working directory /home/ubuntu/pharo-server > Pid file not found: /home/ubuntu/pharo-server/pharo-server.pid > Searching in process list for pharo-server > No pids found! > > > $ logout

July 28, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by StÃ©phane Ducasse

I'm trying to remember what we did with the startup logic. Igor I remember that we made sure that UI cannot start (startup) before UI primitives are allocated because before there was some really strange logic. And this makes sure that servers can work in headless. But I do not see how this can be related. Igor do you have any idea? Stef > We now have builds with Zinc, Kom and Swazoo. > > Zinc is the default for all subsequent builds (Seaside One-Click, > Magritte, Pier). > > Strangely none of the server adaptors works when the image comes up > (Kom and Zinc worked out of the box in Pharo 1.2). After stop and > restart Kom and Zinc work though. > > Swazoo seems to be broken. > > Lukas > > On 28 July 2011 13:20, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> >> On 28 Jul 2011, at 12:54, Lukas Renggli wrote: >> >>> What I want to do next is replace Kom with Zn in Seaside 3.0, Magritte 2 and Pier 2 images. >> >> OK, please let me know ASAP if run into any issues. >> >> Sven >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

July 28, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by Lukas Renggli

> Excellent > Let us know if you find problems because we can bullet profs Zn support for 1.3 Not sure what is going on with Swazoo and Kom. Swazoo doesn't work at all, but doesn't throw an error either (I don't really care about that). Kom does work at startup, but manually starting it works. Stopping the server takes about a minute though. This is kind of strange. Did something with sockets change? Lukas -- Lukas Renggli www.lukas-renggli.ch

July 28, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by StÃ©phane Ducasse

On Jul 28, 2011, at 12:54 PM, Lukas Renggli wrote: > Yep, here: https://twitter.com/renggli/status/96470364368023552 > > I haven't thoroughly tested everything yet, but unit tests pass and > everything works smoothly. > > What I want to do next is replace Kom with Zn in Seaside 3.0, Magritte > 2 and Pier 2 images. Excellent Let us know if you find problems because we can bullet profs Zn support for 1.3 Stef > > Lukas > > On 28 July 2011 12:41, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> Yes, this is very cool indeed. >> >> On 28 Jul 2011, at 11:59, StÃ©phane Ducasse wrote: >> >>> Hi lukas >>> >>> this is cool to see all your projects running on 1.3. >>> I see that somewhere (tweet) but could not find it anymore (too many windows open and too much information). >>> but this is cool. >>> >>> Stef >>> >>> >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

July 28, 2011