<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] About Seaside 3.0</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Oh but existing webservers are already good enough, no? If its internal use only for a couple of two sysadmins, does it really need SSL and such?<BR>
<BR>
Cheers!<BR>
<BR>
-Boris (via BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Sun Jul 13 08:16:29 2008<BR>
Subject: Re: [Seaside] About Seaside 3.0<BR>
<BR>
I haven't been following the details of what Bill is proposing very<BR>
carefully but I can see the point he's trying to make.<BR>
<BR>
Many people may have internal tools written in Seaside. I have<BR>
considered writing a web interface for user management at my current<BR>
job. It would essentially be a tool for administrators and help desk<BR>
staff to perform operations on accounts. Such an application would<BR>
have a half dozen total users, maybe 2 concurrent at maximum. Given<BR>
the sensitivity of some of the information, however, we would<BR>
certainly want the connection encrypted.<BR>
<BR>
Such an application wouldn't need any of the power or reliability of<BR>
Apache really and it certainly isn't a problem for it to be running on<BR>
an alternate port (many of our existing administrative web<BR>
interfaces--including vendor-suplied ones--run on alternate ports).<BR>
<BR>
As long as Apache is the easiest way to set this up, it's not the end<BR>
of the world for me to do so. But if there was a solution available<BR>
that didn't require the extra infrastructure I would certainly<BR>
consider using it. Obviously this isn't going to be the best scaling<BR>
architecture any time soon but that's ok.<BR>
<BR>
I also understand the desire not to have everything re-implemented<BR>
(and then unmaintained) in Smalltalk. But if there's an itch that<BR>
someone wants to scratch and enough users that it ends up being<BR>
maintained, great.<BR>
<BR>
Julian<BR>
_______________________________________________<BR>
seaside mailing list<BR>
seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>