[Seaside] Seaside + JQuery example page on port 9090?
jfitzell at gmail.com
Fri Aug 7 08:01:52 UTC 2009
On Thu, Aug 6, 2009 at 10:03 PM, Philippe
Marschall<philippe.marschall at gmail.com> wrote:
> 2009/8/7 Steve Aldred <aldreds at velocitynet.com.au>:
>> Randal L. Schwartz wrote:
>>>>>>>> "Thierry" == Thierry Thelliez <thierry.thelliez.tech at gmail.com>
>>> Thierry> I was referring to the links on
>>> Thierry> The ones pointing to jQuery, jQueryUI and Scriptaculous.
>>> Those examples are also in the one-click image, as I recall. Just
>>> the image, and run it locally, if you're on a needlessly impaired
>> Needlessly or not if you're living in a bureaucratic organization with a
>> high level of paranoia filters for other than the most common ports exist.
>> If we want Seaside to be widely accessible, all of the demonstration/example
>> code should be available on port 80 and not needlessly moved to some other
>> port. Let the 'experts' hosting the examples map the request however they
>> like but let those in restricted environments be free to explore all that is
>> out there.
> Port 80 requires root privileges. We can't do that.
Erm... The squeak image doesn't have to be running on port 80 - apache
can forward requests to an image on another port same as usual. But
that's not really the point.
My observations are that:
a) this demo is run by someone else, not the Seaside team, so there's
little we can do about what port it's on
b) the server seems to be simply down (at least right now)
c) jQuery is only in Seaside 2.9, which is under heavy development and
still in alpha
d) Once it goes beta, it would probably be a good idea to run the
demos on seaside.st
I don't think any of us are interested in making things difficult for
a few potential users just to prove a point about their firewalls. Is
this why so many sites have big warnings saying "this link goes to an
More information about the seaside