[Seaside] Pharo/Seaside as a back-end for a social media app

[Jan van de Sandt]

On Wed, Aug 29, 2012 at 5:15 AM, Oscar E A Callaú <oalvarez at dcc.uchile.cl>wrote:

> Hi all,
>
>     I plan to build a social media app, initially targeted to iOS clients.
> I was wondering if pharo 1.4 and seaside 3.07/3.1 are enough for a back-end
> where at least these requirements are expected:
>
> + Rest communication (I can use Seaside-REST)
> + Media transmission, ie sending/retrieving Photos and Videos (What
> Seaside modules I can use for this?)
> + Database communication (I can use GlorpDBX)
> + Ouath2 authentification (??, I understand that CouldforkSSO is a client
> not a server)
>

That is correct. CloudforkSSO implements the 'client' side of OAuth2 (and
OAuth1 and OpenID). You can use CloudforkSSO to authenticate your users
against a service provider like Google or Facebook. CloudforkSSO is not an
OAuth2 service provider.


> + Scalability, where I can easily grow from hundreds to thousands of
> clients.
>
> Do you think Pharo could meet that requirements or I must use something
> less cool :-(, such as ruby on rails.
>
> Thanks in advance. I'll really appreciate your comments.
>
> Cheers
>
> P.S.: Sorry, If you received this
> twice._______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20120830/08b29f3a/attachment.htm