On 7/27/07, Chris Lewis <[EMAIL PROTECTED]> wrote:
> I'm quite new to Tapestry and just 2 days ago have started working with
> Tap 5. I realize the two (4 vs 5) are disparately different, but one of
> the things nice about the Tap 4 asset service was the checksum feature I
> mentioned that would deny access unless the sum in the url matched that
> of the file. My newness to Tap may show here, but why can't the asset
> service simply ignore requests for files that are not marked (@Asset) as
> assets? I mean doesn't a deny-all first and allow explicit exceptions
> strategy seem much more sane then providing an open door to the whole
> classpath (class bytes included??)?
If someone adds a JIRA issue I'm pretty sure Howard is able to solve
this in the best interests of T5.
--
regards,
Robin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
