AW: [Seaside] Pharo/Seaside as a back-end for a social media app
hnowak at cincom.com
Fri Aug 31 06:55:15 UTC 2012
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.
Von: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-bounces at 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.
> Thanks in advance. I'll really appreciate your comments.
> P.S.: Sorry, If you received this
> seaside mailing list
> seaside at lists.squeakfoundation.org
seaside mailing list
seaside at lists.squeakfoundation.org
More information about the seaside