X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 84B6D3A3B14 for ; Fri, 5 Nov 2004 05:05:34 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 49650-09 for ; Fri, 5 Nov 2004 05:05:32 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id DD14F3A3B13 for ; Fri, 5 Nov 2004 05:05:32 +0000 (GMT) Received: (qmail 22765 invoked by uid 500); 5 Nov 2004 05:16:46 -0000 Date: Thu, 4 Nov 2004 23:16:46 -0600 From: Bruno Wolff III To: Matt Clark Cc: =?iso-8859-1?Q?Pierre-Fr=E9d=E9ric?= Caillaud , pgsql-performance@postgresql.org Subject: Re: Restricting Postgres Message-ID: <20041105051646.GA22486@wolff.to> Mail-Followup-To: Matt Clark , =?iso-8859-1?Q?Pierre-Fr=E9d=E9ric?= Caillaud , pgsql-performance@postgresql.org References: <003301c4c29a$f052d910$8300a8c0@solent> <418A98C0.9010107@ymogen.net> <418AAF12.8030307@ymogen.net> <418ABC29.8090601@ymogen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <418ABC29.8090601@ymogen.net> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/85 X-Sequence-Number: 9039 On Thu, Nov 04, 2004 at 23:32:57 +0000, Matt Clark wrote: > > > > I think in the future there will be a good bit of presentation > >login in the client... > > Not if Bruno has his way ;-) Sure there will, but it will be controlled by the client, perhaps taking suggestions from the style sheet pointed to by the document. Running foreign code from random or even semi-random places is a recipe for becoming a spam server. See examples from Microsoft such as their spreadsheet and office software. Documents really need to be passive data, not active code. If the client and the server have a special trust relationship, then running code supplied by the server makes sense. So you might use javascript within a business where the IT department runs the server and the employees run clients. However, encouraging people to browse the internet with javascript enabled is a bad idea.