Обсуждение: servlet request expiration

When I am testing my servlet, sometimes I see an exception and know right
away what's causing it. So I fix it in a hurry and put it on the webserver.
But when I hit the refresh button, nothing changes. Sometimes changes occur
instantly, but mostly the changes happen after about five minutes. How can I
make this go faster? 5 minutes may not be very long, but it's still five
minutes are just wasted.

Nico.

IE has a bad habit of caching results.  Set IE up to refresh every time
you hit the page. Also, even though I have it set up that way, I find I
still need to clear the cache and remove all files (Tools | Options |
General | Delete Cookies... and  Tools | Options | General | Delete
Files...).

Give that a shot and see if it helps.  Or use Mozilla, it's safer anyway
and doesn't have the same issue.

Rgds,

Bret


> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Nico
> Sent: Monday, January 10, 2005 8:04 AM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] servlet request expiration
>
> When I am testing my servlet, sometimes I see an exception
> and know right away what's causing it. So I fix it in a hurry
> and put it on the webserver.
> But when I hit the refresh button, nothing changes. Sometimes
> changes occur instantly, but mostly the changes happen after
> about five minutes. How can I make this go faster? 5 minutes
> may not be very long, but it's still five minutes are just wasted.
>
> Nico.
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>

"Nico" <nicohmail-postgresql 'at' yahoo.com> writes:

> When I am testing my servlet, sometimes I see an exception and know right
> away what's causing it. So I fix it in a hurry and put it on the webserver.
> But when I hit the refresh button, nothing changes. Sometimes changes occur
> instantly, but mostly the changes happen after about five minutes. How can I
> make this go faster? 5 minutes may not be very long, but it's still five
> minutes are just wasted.

This really has nothing to do with the postgres JDBC driver.

--
Guillaume Cottenceau