January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Zinc-WebSockets Live Demo

by Norbert Hartl

Am 09.01.2013 um 16:11 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Norbert, > > On 09 Jan 2013, at 14:57, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Am 09.01.2013 um 14:30 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> Since most proxies and load balancers, most notably Apache, don't handle the WebSocket protocol very well, the only solution is to arrange for direct connections to the Smalltalk image. >> >> Who's interested in load balancing for websockets should look at HAProxy (http://haproxy.1wt.eu/) >> >> FYI, >> >> Norbert > > Yeah, I knew that HAProxy seems to be able to do it, but I didn't want to learn how to deal with the complexity of yet another technology stack. There is also the fundamental question whether it makes sense to proxy/tunnel the semi-permanent WebSocket connections. You would consume twice the resources while gaining little. > Agreed about yet another stack. But I don't think there is something like a fundamental question about those things. In my experience the first or second new requirement to your project always proves you wrong :) There are often use cases where it is inevitable to have a single entry point, have balancing even for TCP connections, pinning, etcâ¦ > Have you used HAProxy ? For WebSockets too ? I used HAProxy 5 years ago or so. But I'm referring to the experience of a friend of mine who actually uses it in production for http://www.userlike.de/. He uses Socket.IO for the chat connections and there are requirements he needs to use something like HAProxy. Btw. my post wasn't meant to "you should use HAProxy". I just wanted to give some hints for people who feel they need for it. Norbert

Jan. 9, 2013

Re: [Pharo-project] Zinc-WebSockets Live Demo

by Sven Van Caekenberghe

Norbert, On 09 Jan 2013, at 14:57, Norbert Hartl <norbert(a)hartl.name> wrote: > Am 09.01.2013 um 14:30 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> Since most proxies and load balancers, most notably Apache, don't handle the WebSocket protocol very well, the only solution is to arrange for direct connections to the Smalltalk image. > > Who's interested in load balancing for websockets should look at HAProxy (http://haproxy.1wt.eu/) > > FYI, > > Norbert Yeah, I knew that HAProxy seems to be able to do it, but I didn't want to learn how to deal with the complexity of yet another technology stack. There is also the fundamental question whether it makes sense to proxy/tunnel the semi-permanent WebSocket connections. You would consume twice the resources while gaining little. Have you used HAProxy ? For WebSockets too ? Sven

Jan. 9, 2013

Re: [Pharo-project] jenkins slave disk space

by Camillo Bruni

almost done! On 2013-01-09, at 13:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > On Jan 9, 2013, at 11:08 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> our pharo-linux64 bit slave is down due to disk space limitations. >> this is mainly caused by the ~6GB android SDK ;) >> which takes around the same space as the whole workspace under /builds >> >> Solutions: >> ========== >> a) condense the android sdk >> b) create a slave with a bigger disk >> > > c) associate a disk with it and move the /builds/ there. > > With CloudStack behind, it should be possible to create e.g. a 50 or 100GB volume and > mount it as /builds/ > > Marcus

Jan. 9, 2013

Re: [Pharo-project] Zinc-WebSockets Live Demo

by Norbert Hartl

Am 09.01.2013 um 14:30 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Since most proxies and load balancers, most notably Apache, don't handle the WebSocket protocol very well, the only solution is to arrange for direct connections to the Smalltalk image. Who's interested in load balancing for websockets should look at HAProxy (http://haproxy.1wt.eu/) FYI, Norbert

Jan. 9, 2013

Re: [Pharo-project] [Update] Zinc-SSO OAuth 1.0 & OpenID Alpha Code & Live Demos

by StÃ©phane Ducasse

On Jan 9, 2013, at 2:32 PM, Sven Van Caekenberghe wrote: > > On 09 Jan 2013, at 14:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> What I like with you sven is the documentation :) >> I love it. > > Thanks. > > But we still have to do a lot more documenting, both high level as well as in the codeâ¦ yes but still I love that people consider documentation. > > Sven

Jan. 9, 2013

Re: [Pharo-project] Smalllint for Traits

by Damien Cassou

n Wed, Jan 9, 2013 at 2:04 AM, aizcorbe <juansebastian.aizcorbe(a)gmail.com> wrote: > I hope you find this useful. sure we do, thank you very much. Unfortunately, we are mainly focused on Pharo 2.0 currently. Would you mind porting your work to Pharo 2.0? I created the issue to track your work: http://code.google.com/p/pharo/issues/detail?id=7223 Best -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 9, 2013

Re: [Pharo-project] [Update] Zinc-SSO OAuth 1.0 & OpenID Alpha Code & Live Demos

by Sven Van Caekenberghe

On 09 Jan 2013, at 14:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > What I like with you sven is the documentation :) > I love it. Thanks. But we still have to do a lot more documenting, both high level as well as in the codeâ¦ Sven

Jan. 9, 2013

[Pharo-project] Zinc-WebSockets Live Demo

by Sven Van Caekenberghe

Hi, Yesterday I deployed a live demo of Zinc-WebSockets http://websocket.stfx.eu Since most proxies and load balancers, most notably Apache, don't handle the WebSocket protocol very well, the only solution is to arrange for direct connections to the Smalltalk image. Deploying and running this code in your own image is pretty easy: ConfigurationOfZincHTTPComponents project latestVersion load: 'WebSocket'. ZnServer startDefaultOn: 1701. ZnWebSocketDelegate installExamplesInDefaultServer. Then open http://localhost:1701/ws-demo with your browser. Sven PS: You can read more about Zinc-WebSockets here https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md PS: This demo, like the standard Zn and SSO demos run in the very latest Pharo 2.0 version http://zn.stfx.eu/status http://sso.stfx.eu/status http://websocket.stfx.eu:9999/status http://websocket.stfx.eu:9999/ws-status-client -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Jan. 9, 2013

Re: [Pharo-project] [Update] Zinc-SSO OAuth 1.0 & OpenID Alpha Code & Live Demos

by StÃ©phane Ducasse

What I like with you sven is the documentation :) I love it. > Hi, > > Here is another update regarding the Zinc-SSO project. > > http://lists.gforge.inria.fr/pipermail/pharo-project/2012-December/072658.h… > > Jan has been porting his earlier CloudforkSSO work to Zinc-SSO so that we now have support for both OAuth1 and OpenID. Both are considerably more complex than OAuth2 that was implemented earlier. The codebase was cleaned up a bit and more test/demo code was added. > > Some basic documentation and loading instructions can be found at > > https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md > > Basically you should be able to get all the bits (preferably in Pharo 2.0) by doing > > (ConfigurationOfZincHTTPComponents project version: '2.2') load: 'SSO' > > This is not a subject where loading some code gives you a working demo since there is some setup to be done. Therefor we orginanized two live demos: > > http://sso.stfx.eu > http://sso.doit.st > > There is now support for Google, Microsoft, Facebook, Twitter & Yahoo. The second demo is slight more extensive: it even allows you to do Twitter posts ! > > Although the code is not yet production quality, we could use some feedback from early adopters to help use shake out remaining problems. > > Jan & Sven > > PS: We would like to thank Andy Burnett of Knowinnovation Inc and ESUG for sponsoring this open source work. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Jan. 9, 2013

Re: [Pharo-project] jenkins slave disk space

by Marcus Denker

On Jan 9, 2013, at 11:08 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > our pharo-linux64 bit slave is down due to disk space limitations. > this is mainly caused by the ~6GB android SDK ;) > which takes around the same space as the whole workspace under /builds > > Solutions: > ========== > a) condense the android sdk > b) create a slave with a bigger disk > c) associate a disk with it and move the /builds/ there. With CloudStack behind, it should be possible to create e.g. a 50 or 100GB volume and mount it as /builds/ Marcus

Jan. 9, 2013