tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tapestry-...@jakarta.apache.org
Subject [Jakarta Tapestry Wiki] Updated: WishList
Date Thu, 16 Dec 2004 15:08:13 GMT
   Date: 2004-12-16T07:08:13
   Editor: JohnReynolds <john.t.reynolds@gmail.com>
   Wiki: Jakarta Tapestry Wiki
   Page: WishList
   URL: http://wiki.apache.org/jakarta-tapestry/WishList

   no comment

Change Log:

@@ -1,3 +1,5 @@
+ * Add support for components that use XMLHttpRequest.  XMLHttpRequest (or something similar)
is supported by Microsoft, Mozilla, Safari, and Opera.  Basically, Javascript can request
information from the server and update a portion of a page rather then refreshing the whole
page.  An example of a component that could benefit from this would be a derivative of the
DatePicker component that could be used for scheduling appointments.  As the user selects
a month, the "already reserved slots" could be retrieved from the server to update the component.
 While it is not strictly necessary for Tapestry to govern the conversation between the component
and the server, there are many benefits in doing so.  For example, if the client's browser
does not support XMLHttpRequest it will be necessary to refresh the entire page, and Tapestry
would definitely handle that task.
  * Add support for DHTML components.
  * How about a Tapestry Context? I've built one for our projects, it sets the Visit into
ThreadLocal. This way, helper classes don't have to pass around the Visit. The extended BasePage
implements IPageListener and sets (and unsets) the Visit. Classes that control web flow can
grab it themselves. You could also put HttpRequest in it for implementing Portal support (this
was mentioned in HLS's post as problematic). Probably all of a 30 minute job.

To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message