Do you mean javascript validation? The beanform seems to support using things
like scriptalicious to implement client-side validation (of the declarative
constraints specified at the page level). I didn't see any evidence that the
"leaf" core components support this.
I did find some info at:
http
Thiago H. de Paula Figueiredo wrote:
>
> Have you done any profiling to know exactly how much time your application
> is spending rendering? Most of the time bottlenecks are in other places
> (specially in the database).
>
It's not really the rendering that I'm concerned about but rather
Thanks for the response Ville,
Caching the component wont always work well since these are dynamically
rendered. Certainly we will consider caching when appropriate but, for
example, sometimes it's specialized by the user.
Also, much of this content is provided by non-Tapestry sources (we have
Just realized I need to clarify something... the future would be making an
HTTP request to retrieve the raw HTML (aka the "guts") of the component and
that would get inserted into the final DOM verbatim.
--
View this message in context:
http://www.nabble.com/Using-%22futures%22-to-parallelize-re
We have an app that's an aggregation of several 'components' (not yet written
in Tapestry... using an older in-house framework). Although each component
is not very expensive to create, the aggregate cost can get kinda high
sometimes.
I've been poking around Tapestry for the past couple of days t
