tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jakarta-tapestry Wiki] Update of "Tapestry41Roadmap" by JesseKuhnert
Date Mon, 23 Jan 2006 06:40:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-tapestry Wiki" for change
notification.

The following page has been changed by JesseKuhnert:
http://wiki.apache.org/jakarta-tapestry/Tapestry41Roadmap

------------------------------------------------------------------------------
  
   * Shell: The current Shell component is the main barrier to being able to easily contribute
global resources, such as css/javascript inclusions from component libraries. A refactoring
of the Shell and some of the asset service notions will enable component libraries to conditionally
be able to contribute their assets to the head portion of html pages via the Shell in a much
easier manner.
  
-  * '''Done(01/05/06)''' ''Relative/Unprotected Resources: The current AssetService requires
that all resources be tracked and validated against an md5sum digest in order to provide security
against malicious users. This scheme works, but also limits the ability for people to do more
dynamic things, like optionally include image assets within css spec files, or to do library
inclusion requests on resources not previously digested (as with dojo javascript toolkit).
Refactorings here should result in a new notion of "unprotected" resources that don't require
any special security considerations. These resources and the pattern that describes them will
be completely configurable via hivemind configuration points.'' 
+  * '''Done(01/05/06)''' Relative/Unprotected Resources: The current AssetService requires
that all resources be tracked and validated against an md5sum digest in order to provide security
against malicious users. This scheme works, but also limits the ability for people to do more
dynamic things, like optionally include image assets within css spec files, or to do library
inclusion requests on resources not previously digested (as with dojo javascript toolkit).
Refactorings here should result in a new notion of "unprotected" resources that don't require
any special security considerations. These resources and the pattern that describes them will
be completely configurable via hivemind configuration points.
+ 
+  * [BuildingDojo] New javascript package library inclusions in tapestry.
  
  == Component Identities/Rewind Cycle/URL rewriting ==
  A much more impactual and overarching change to the framework will hopefully result in a
unified system for identifying and dealing directly with components, as well as improving
overall handling of form input field value parsing. These changes will result in a number
of great improvements, the least of which will allow a very dynamic and intuitive request
cycle for handling ajax style logic.

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


Mime
View raw message