<br><br><div class="gmail_quote">On Wed, Aug 29, 2012 at 5:15 AM, Oscar E A Callaś <span dir="ltr"><<a href="mailto:oalvarez@dcc.uchile.cl" target="_blank">oalvarez@dcc.uchile.cl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
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:<br>
<br>
+ Rest communication (I can use Seaside-REST)<br>
+ Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?)<br>
+ Database communication (I can use GlorpDBX)<br>
+ Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server)<br></blockquote><div><br></div><div>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.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+ Scalability, where I can easily grow from hundreds to thousands of clients.<br>
<br>
Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails.<br>
<br>
Thanks in advance. I'll really appreciate your comments.<br>
<br>
Cheers<br>
<br>
P.S.: Sorry, If you received this twice._______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br>