[Seaside] Seaside + JQuery example page on port 9090?
aldreds at velocitynet.com.au
Fri Aug 7 01:03:12 UTC 2009
Miguel Enrique Cobá Martinez wrote:
> 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.
You and Randal are assuming that you have control of the firewall, that
was not where this discussion started.
In many large organizations those who do control the firewalls will not
change their policies regardless of how inane they are.
Why exclude interested people just because some other decision makers in
their organizations are idiots?
More information about the seaside