I was just throwing out an idea, thinking off the top of my head, what about having a bean that is active throughout the session and having a flag in it that changes every time the trigger is "triggered", which in turn updates or refreshes the client side...I don't know if this can work...
-----Original Message-----
From: Joe Cheng [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 01, 2001 11:31 AM
To: [EMAIL PROTECTED]
Subject: Re: help me
>> How about using a trigger on the database that instantly knows when the
data has changed, like that no unnecessary refreshes have to be done on the
client side when the data hasn't been changed? <<
Can you elaborate? So the database tells some server-side Java code that
the data has been changed... now how do you get that information down to the
web browser?
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://archives.java.sun.com/jsp-interest.html
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.jsp
http://www.jguru.com/faq/index.jsp
http://www.jspinsider.com
