Posted tagged ‘pharo’

CloudforkSSO on Pharo with stunnel

February 23, 2011

The latest version of CloudforkSSO (version 1.1.0) on Pharo uses the Zinc-HTTP library. This library contains a good http client. Actually it contains multiple http clients, depending on your requirements you can pick one of them. One feature Zinc-HTTP doesn’t support (yet?) is secure http. Most of the OAuth and OpenID providers require https connections [...]

CloudforkSSO – OpenID and OAuth support for Smalltalk

February 15, 2011

With the CloudforkSSO library you can let the users of your Seaside web application login using their Google or Yahoo accounts. This works using the OpenID2 protocol. CloudforkSSO also contains OAuth support. With this protocol you can ask users for permission to access their data on other websites. Some providers that you can integrate with: [...]

EC2 AMI with Smalltalk and Seaside: Update 3

October 10, 2010

Today I published a new version of the Amazon EC2 image with Smalltalk and Seaside. The third version contains the following software: Ubuntu Server 32bit 10.04 LTS (release 2010-09-23) Apache HTTP Server 2.2 SqueakVM 4.0.3.2202 Unix VM PharoCore 1.1.1 Seaside 3.0 The AMI identification: ami-c2fe0aab The update to the Ubuntu server makes it easier to [...]

Creating a Seaside runtime image with Pharo

September 8, 2010

For the ec2 machine image with Seaside I prepared an image with only the runtime packages of Seaside. The image was based on PharoCore 1.1. This is the core Pharo image without development tools and extra libraries. The Seaside development tools can be very convenient during development but in a production environment they can be [...]

A new public EC2 AMI with Smalltalk and Seaside

August 29, 2010

This weekend I created a public Amazon Machine Image (AMI) setup as a Smalltalk web server with a Linux SqueakVM, a Pharo 1.1 Smalltalk image and the Apache2 web server. Anyone can use this AMI as a robust and scalable runtime platform for their Seaside applications. In this article I will try to explain how [...]

HTTP Clients for Squeak

May 25, 2009

Cloudfork-AWS makes the Amazon Web Services (AWS) S3, SQS and SimpleDB easily accessible from Smalltalk. All the communication between the Smalltalk image and AWS is done via HTTP. So a HTTP Client is an important requirement for Cloudfork-AWS. Cloudfork-AWS needs more than just handling simple HTTP GET and POST requests, the following features are also [...]


Follow

Get every new post delivered to your Inbox.