Ok, this thread has nothing to do with Struts, so I will make one more pass at it. After this, I'd suggest doing some prototypes and seeing what works best - trial and error with multiple quick prototypes is better learning than asking others to do the work for you.
Now, a database can store more than one row for a user, so I'm not understanding why you would store a list of messages in XML format in the database. If databases are new to you, I'd suggest reading a good book on relational DB theory and application. If there is a business or technical reason why you need XML - great, use it! As for what you are trying to do, I think there have been a number of options presented to you, from using JMS to a database to store the messages in either a transient or persistent manner. None of them are actually related to Struts, as Struts is a presentation layer, nothing more. The task you are trying to do is separate from Struts, other than you possibly writing some common Struts code that will offer the necessary lookup of the messages for a user. Try coding some of the solutions and your own with your associates and see how they turn out. Good Luck! James > -----Original Message----- > 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 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 to get around. > > > 9/23/2002 3:03:49 PM, "Galbreath, Mark" <[EMAIL PROTECTED]> wrote: > > >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 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 the implications of that, so maybe this is a bad > suggestion ;-) > > > >Vernon Wu wrote: > > > >>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 how the > >>notification > >shall be implemented. I only use a web > >>container, and considering to add in a JMS server for IM. > >> > >>Any suggestions? > >> > >>Thanks, > >> > >>Vernon > >> > > > >-- > >Eddie Bush > > > > > > > > > >-- > >To unsubscribe, e-mail: > ><mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: > ><mailto:[EMAIL PROTECTED]> > > > >-- > >To unsubscribe, e-mail: > <mailto:struts-user-> [EMAIL PROTECTED]> > >For > additional commands, > e-mail: > ><mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > To unsubscribe, e-mail: > <mailto:struts-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
