[Seaside] Seaside + JQuery example page on port 9090?
boris at deepcovelabs.com
Fri Aug 7 00:54:52 UTC 2009
Okay, something has definitely gone amiss in this thread ;) The original report was simply that the public demo may not be accessible from certain environments, which is akin to reporting a dead link IMHO. The maintainer of that specific demo site has two options: a) ignore it or b) do something about it. It is well known and documented what that person needs to do to expose Seaside services via port 80 should they choose option b) and wasn't the subject of this thread at all.
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Miguel Enrique Cobá Martinez
Sent: Thursday, August 06, 2009 5:25 PM
To: dave.bauer at gmail.com; Seaside - general discussion
Subject: Re: [Seaside] Seaside + JQuery example page on port 9090?
El jue, 06-08-2009 a las 20:10 -0400, Dave Bauer escribió:
> On Thu, Aug 6, 2009 at 8:06 PM, Randal L. Schwartz<merlyn at stonehenge.com> wrote:
> >>>>>> "Boris" == Boris Popov <boris at deepcovelabs.com> writes:
> > Boris> I agree. In fact many personal firewall products also block uncommon
> > Boris> ports such as this one and only leave things like 80, 443, 25 etc by
> > Boris> default.
> > That's completely nuts.
> > There's nothing more "dangerous" at port 9090 than at port 80.
> > Anyone who constructs such a firewall is hopelessly naive, and if
> > you're using such a product, turn it off, and demand a refund.
> That is totally besides the point. Unfortunately the Seaside community
> regularly tries to scare away those interested in the product by
> giving unhelpful advice.
If I am developing web applications and am not capable of configure or
find the cause of my net issues I have a deeper problem that I think and
it is not fault on the Seaside community.
> Everyone expects publically available web sites to be on port 80.
> Anyone who is trying to market a web site product should understand
> that people will expect stuff to be available on port 80, and also
> understand the technique to make it available that way.
First, the "everyone" your are refering not even know what a port is.
they just write a url on the browser or better, go to google, find
something and click on a link. NO ports in the process.
Second, the fact that an webapps runs in a specific port doesn't says
nothing about the quality of the product. Rails runs on port 3000,
Tomcat in 8180. That is just a simple random port.
When you buy a domain, put your server in production then you can omit
the port by running on a standard port (80 for http) but even so, if you
are on unix/mac you can't run a server on a port below 1024 so you must
use Apache/Lighttpd to listen on 80 and proxy to the other port (3000,
8180, 8080, 9090, etc). To the user the service is running on "port 80"
but actually isn't.
So don't blame the comunnity, they are trying to help but not resolve
*all* your problems. At the end, everyone must do their homework.
> > --
> > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
> > <merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
> > Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
> > See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
> > _______________________________________________
> > seaside mailing list
> > seaside at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside mailing list
seaside at lists.squeakfoundation.org
More information about the seaside