-
From: Vernon Wu [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 6:49 PM
To: Struts Users Mailing List
Subject: Re: RE: User Notification
What else would you suggest?
The reason I am thinking about use DOM is that messages are
stored in a XML format in DB since
Absolutely use SAXP (java.sun.com) or JDOM (www.jdom.org) to parse the XML
in a messaging system! DOM parsing would be a big bottleneck on any
high-traffic system.
Mark
-Original Message-
From: Vernon Wu [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 7:49 PM
The reason I
, September 23, 2002 4:49 PM
To: Struts Users Mailing List
Subject: Re: RE: User Notification
What else would you suggest?
The reason I am thinking about use DOM is that messages are
stored in a XML format in DB since the number of
messages can vary. The XML format data needs
True, but I'd like to hear more about what people are doing as far as
integrating XSLT into a Struts app. Seems like every time I pick up a tech
rag, SOAP and XML/XSLT are on the cover.
Mark
-Original Message-
From: James Higginbotham [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September
I've had to implement mail like systems like this in a variety of
places. If I could just make some suggestions:
1) Notification is usually accomplished as a side-effect of how you
store your messages. For instance, if each message is stored with a
read-flag, then it's a simple query to find
I need to implement a message system, sort like email but inside the Java web
application only for its users. After one
user, A, sends a message to another, B, B shall be notified to retrieve the updated
messages if B is on line. I plan to
implement messages as stored in a DOM. My question is
Sounds like a simple DB-lookup to me. You aren't going to update the
client until they refresh at page at least. You'd just have to include
something that polled for new messages in each page you wanted them to
receive notification. I'm not familiar with what you mean by stored as
a DOM or
I want to have a better implementaiton over unnecessary DB access. That is the reason
I would like to use a
notification mechanism.
9/23/2002 2:41:05 PM, Eddie Bush [EMAIL PROTECTED] wrote:
Sounds like a simple DB-lookup to me. You aren't going to update the
client until they refresh at
I hope he means stored as an XML doc. Parsing DOMs are notoriously slow.
-Original Message-
From: Eddie Bush [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 5:41 PM
Sounds like a simple DB-lookup to me. You aren't going to update the
client until they refresh at page at
signed in,
they will never get the message (thus, see option 1 and previous posts
to this list).
James
-Original Message-
From: Vernon Wu [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 1:44 PM
To: Struts Users Mailing List
Subject: Re: User Notification
I want
Yeah you could persist it to a DB though and show the message from the
DB when they ask to do that... and just rely on your
session-manager-thingie for notification.
James Higginbotham wrote:
Ok, then you could use JMS to store a message in a topic and check for
it on each request to show the
I don't follow you. Can you explain with more details?
9/23/2002 3:55:04 PM, Eddie Bush [EMAIL PROTECTED] wrote:
Yeah you could persist it to a DB though and show the message from the
DB when they ask to do that... and just rely on your
session-manager-thingie for notification.
James
What else would you suggest?
The reason I am thinking about use DOM is that messages are stored in a XML format in
DB since the number of
messages can vary. The XML format data needs to be parsed either SAX or DOM. If DOM
parsing is too slow, SAX
parsing into a collection object is a way
a horse of a different color
peace,
Joe
-Original Message-
From: Vernon Wu [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 4:49 PM
To: Struts Users Mailing List
Subject: Re: RE: User Notification
What else would you suggest?
The reason I am thinking about
I was expounding on James' response - saying that you could actually
persist the message somewhere on top of what he suggest for the session
manager. If you persist the messages, they will be there when the user
arrives. You would have to do an initial check for messages when they
login,
15 matches
Mail list logo
