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) + 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.
On Wed, Aug 29, 2012 at 5:15 AM, Oscar E A Callaú oalvarez@dcc.uchile.clwrote:
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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
On Wed, Aug 29, 2012 at 5:15 AM, Oscar E A Callaú oalvarez@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)
Yes
- Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?)
You usually want to avoid passing files through the image. A combination of mod_fileupload [1] and mod_xsendfile [2] or something similar may work.
- Database communication (I can use GlorpDBX)
There are drivers available for various RDBMS. You'll have to check for the specific one you want to use. If you want to use an ORM on top of OpenDBX then you can use GlorpDBX. Depending on the concurrency level and query latencies you expect OpenDBX may not be ideal. However there are "native" (socket based) drivers for PostgreS and MySQL that don't have these issues.
- Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server)
- Scalability, where I can easily grow from hundreds to thousands of clients.
I would say this mostly depends on your architecture. You should certainly test first.
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.
[1] http://apache.webthing.com/mod_upload/ [2] https://tn123.org/mod_xsendfile/
Cheers Philippe
On Aug 29, 2012, at 5:15 AM, Oscar E A Callaú 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)
- 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.
Pharo is not your only Smalltalk (Seaside) option. You can develop in Pharo and deploy in GemStone, avoiding the database communication complications and scale.
James Foster
Thanks in advance. I'll really appreciate your comments.
Cheers
P.S.: Sorry, If you received this twice._______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Absolutely! Pharo is not your only option to do cool Seaside. Besides GemStone there is VA Smalltalk. And there is Cincom Smalltalk.
Your true requirements with regards to performance and scalability you'll only find out once you deploy. As had been said before: test! Test! Test! Remember: Make It Work, Make It Right, Make It Fast.
HTH Helge
-----Ursprüngliche Nachricht----- Von: seaside-bounces@lists.squeakfoundation.org [mailto:seaside-bounces@lists.squeakfoundation.org] Im Auftrag von James Foster Gesendet: Donnerstag, 30. August 2012 21:15 An: Seaside - general discussion Betreff: Re: [Seaside] Pharo/Seaside as a back-end for a social media app
On Aug 29, 2012, at 5:15 AM, Oscar E A Callaú 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) 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.
Pharo is not your only Smalltalk (Seaside) option. You can develop in Pharo and deploy in GemStone, avoiding the database communication complications and scale.
James Foster
Thanks in advance. I'll really appreciate your comments.
Cheers
P.S.: Sorry, If you received this twice._______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Thanks guys for your comments.
Cheers
On Aug 31, 2012, at 2:55 , Nowak, Helge wrote:
Absolutely! Pharo is not your only option to do cool Seaside. Besides GemStone there is VA Smalltalk. And there is Cincom Smalltalk.
Your true requirements with regards to performance and scalability you'll only find out once you deploy. As had been said before: test! Test! Test! Remember: Make It Work, Make It Right, Make It Fast.
HTH Helge
-----Ursprüngliche Nachricht----- Von: seaside-bounces@lists.squeakfoundation.org [mailto:seaside-bounces@lists.squeakfoundation.org] Im Auftrag von James Foster Gesendet: Donnerstag, 30. August 2012 21:15 An: Seaside - general discussion Betreff: Re: [Seaside] Pharo/Seaside as a back-end for a social media app
On Aug 29, 2012, at 5:15 AM, Oscar E A Callaú 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) 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.
Pharo is not your only Smalltalk (Seaside) option. You can develop in Pharo and deploy in GemStone, avoiding the database communication complications and scale.
James Foster
Thanks in advance. I'll really appreciate your comments.
Cheers
P.S.: Sorry, If you received this twice._______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside@lists.squeakfoundation.org
-
James Foster -
Jan van de Sandt -
Nowak, Helge -
Oscar E A Callaú -
Philippe Marschall