Skip site navigation (1) Skip section navigation (2)

Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL

From: Kris Jurka <books(at)ejurka(dot)com>
To: <listas(at)lozano(dot)eti(dot)br>
Cc: Rick Gigger <rick(at)alpinenetworking(dot)com>,"Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>,Randolf Richardson <rr(at)8x(dot)ca>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Triggers, Stored Procedures, PHP. was: Re: PostgreSQL
Date: 2004-01-31 01:17:44
Message-ID: Pine.LNX.4.33.0401302015340.1439-100000@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-general

On Fri, 30 Jan 2004 listas(at)lozano(dot)eti(dot)br wrote:

> Hi,
>
> > > Web applications should NEVER fork processes or create their own threads.
> > > Period. Do this isn't safe in any environment, os, web server or
> > development
> > > tool. You can see on the J2EE specs that Servlets and EJBs are expressly
> > > prohibited from doing this.
> >
> > Is this true?  I know lots of servelet developers (mostly using Tomcat) that
> > do this all the time without encountering any problems.  Could you point me
> > to the part in the spec where it indicates that this is inappropriate?
>

This was recently discussed on the jdbc list here:

http://archives.postgresql.org/pgsql-jdbc/2003-12/threads.php

The general consensus was that threads are legal in servlets.

Kris Jurka


In response to

pgsql-general by date

Next:From: listasDate: 2004-01-31 02:05:02
Subject: Re: IDENT and pg_hda.conf
Previous:From: Martijn van OosterhoutDate: 2004-01-31 01:06:47
Subject: Re: DB cache size strategies

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group