  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Design discussion | Design discussion 2005-04-13 - By Sean Brydon
Back Hi,
In the Java BluePrints Solutions Catalog project on java.net, we have starting covering the usage of AJAX in J2EE applications. It is early access, and an emerging technology, so will change a lot, but we have some documents describing some common problems and solutions, as well as some sample applications.
You can check it out at https://bpcatalog.dev.java.net/nonav/ajax/index.html
hope that helps, Sean Bayarsaikhan VOLODYA (YAZ-ArGe) wrote:
> i absolutely agree with ramnish. > using javascript with xml is cleanest and simplest way to do this. > like gmail does. > > -- --Original Message-- -- > *From:* An interest list for Sun Java Center J2EE Pattern Catalog > [mailto:J2EEPATTERNS-INTEREST@(protected)]*On Behalf Of *Ramnish > Kalsi > *Sent:* 12 Nisan 2005 Sal? 19:43 > *To:* J2EEPATTERNS-INTEREST@(protected) > *Subject:* Re: Design discussion > > On the client side, the technology which google uses is also > pretty clean - AJAX - Asynchronous javascript and xml. > There are some good discussions about this on serverside.com > > But, depends upon, how you want to divide the responsibilities > between client and server. > > ramnish. > > -- --Original Message-- -- > *From:* An interest list for Sun Java Center J2EE Pattern Catalog > [mailto:J2EEPATTERNS-INTEREST@(protected)]*On Behalf Of *jon > *Sent:* 12 April 2005 17:38 > *To:* J2EEPATTERNS-INTEREST@(protected) > *Subject:* Re: Design discussion > > * > I saw a product once that used Javascript to interact with an > applet, which then established network connections on its > behalf. I think in that case it was only using straight > "pull" HTTP requests, but presumably you could open a > connection that would accept a server-initiated "push". > > I would expect such an approach to be pretty involved, but you > might want to research it more. > > Regards, > Jon Petruk > > > On Tue, 12 Apr 2005 12:22:07 -0400, Vijay K Dasari wrote* > > In Client/ Server model using thick clients like SWING, we > can use an Observer Pattern ( Publish/Subscribe ), where > > the client subscribes to the messages. when the server gets > a new message, it can notify all the subscribers(users). > > > > As Web (HTTP) is stateless, the client has to ask the server > for the new messages. > > Client can make request to a servlet(which tells whether the > user has any new messages) at certain time intervals. > > In html we can use the "Refresh" metatag. which looks > something like > > > > <meta http-equiv="Refresh" > content="1800;URL=/servlet/checkNewMessages.do"/> > > > > > > Vijay. > > > > > > > > -- --Original Message-- -- > > *From:* An interest list for Sun Java Center J2EE > Pattern Catalog > [mailto:J2EEPATTERNS-INTEREST@(protected)]*On Behalf Of > *Maya menon > > *Sent:* Tuesday, April 12, 2005 11:36 AM > > *To:* J2EEPATTERNS-INTEREST@(protected) > > *Subject:* Design discussion > > > > > > Our client/server application which work realtime: > > Currently we have a client/server application. Our users > log into the client and the system delivers messages to > the users. > > when a new message arrives the users see a signal > flashing and therby gets notified about the > > new message. > > > > Now this client needs to be transformed into a web based > system. > > > > Instead of the clients logging into the client window, > now the users log into the web site. > > The same feature has to be provided. > > when a new message arrives the users have to see a > signal flashing and therby gets notified about the > > new message. > > Can you all please suggest a good J2ee design approach > for this ? > > > > How do we enable the flashing signal ? I need some > suggestions. > > > > Thanks, > > > > > > > -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -- -- ---- > Do you Yahoo!? > > Yahoo! Mail - Find what you need with new enhanced > search. Learn more. > <http://us.rd.yahoo.com/evt=29917/*http://info.mail.yahoo.com /mail_250> > ================================================================= === > Companion Site: http://www.corej2eepatterns.com J2EE > BluePrints: > http://java.sun.com/blueprints/corej2eepatterns List > Archive: > http://archives.java.sun.com/archives/j2eepatterns-interest.html > Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to > listserv@(protected) > > > > > __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __ > > > This email has been scanned by the MessageLabs Email > Security System. > > For more information please visit > http://www.messagelabs.com/email > > > __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __ > > > > ==================================================================== > Companion Site: http://www.corej2eepatterns.com J2EE > BluePrints: http://java.sun.com/blueprints/corej2eepatterns > List Archive: > http://archives.java.sun.com/archives/j2eepatterns-interest.html > Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to > listserv@(protected) > > > -- > Jonathan Petruk > J. Petruk Consulting Inc. > E-mail: jon@(protected) > phone: 905-668-9209 fax: 905-668-4728 > http://www.petruk.net/ > > ==================================================================== > Companion Site: http://www.corej2eepatterns.com J2EE > BluePrints: http://java.sun.com/blueprints/corej2eepatterns > List Archive: > http://archives.java.sun.com/archives/j2eepatterns-interest.html > Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to > listserv@(protected) > > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > > www.mimesweeper.com > ********************************************************************** > ==================================================================== > Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: > http://java.sun.com/blueprints/corej2eepatterns List Archive: > http://archives.java.sun.com/archives/j2eepatterns-interest.html > Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to > listserv@(protected) > > ==================================================================== > Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: > http://java.sun.com/blueprints/corej2eepatterns List Archive: > http://archives.java.sun.com/archives/j2eepatterns-interest.html > Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to > listserv@(protected)
==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
 |