From: Leo Brewin <leo.brewin@internode.on.net>
Subject: Re: aws, gnoga or raw html?
Date: Sun, 8 Feb 2015 14:21:55 -0800 (PST)
Date: 2015-02-08T14:21:55-08:00 [thread overview]
Message-ID: <e65234e4-7172-477c-9a6a-fcc7dac179b7@googlegroups.com> (raw)
In-Reply-To: <b101a68a-77a4-47ce-bef6-9110a46086f8@googlegroups.com>
On Friday, February 6, 2015 at 9:23:39 AM UTC+11, David Botton wrote:
> AWS would just be another web server. You would server the same pages and you would use Ada instead of say PHP or Python.
>
> Gnoga is a completely different concept. You build an application as you would a desktop application accept it is running on the web. You could use Gnoga in the same way as AWS as well since it has a built in Web server, etc.
>
> I recently added (as in last night) to Gnoga the ability to auto fall back to http long polling and Ajax when Websockets are not available. What that means is that you won't have to worry about firewall issues, etc. and use a Gnoga application for "website" development is very reasonable.
>
> So to answer, if you plan on doing anything more than server static pages or occasional form submissions, Gnoga is probably the best option today (in any language) if you want anything interactive.
>
> David Botton
Hi David,
Many thanks for the reply. I'll go away and have a play with AWS and Gnoga.
Cheers,
Leo
prev parent reply other threads:[~2015-02-08 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 21:59 aws, gnoga or raw html? Leo Brewin
2015-02-05 22:23 ` David Botton
2015-02-06 2:44 ` johannes falcone
2015-02-06 7:25 ` David Botton
2015-02-08 22:21 ` Leo Brewin [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox