You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2009/02/10 01:30:24 UTC
Re: patching ticket TAP5-423
Have you thought through the implications of exposing the file system?
Seems like you would need some configuration to support a root
directory (which you wouldn't want to be "/").
I think, after that, it would tend to follow the lead of the
ContextAssetFactory and the related AssetDispatcher code.
Perhaps there needs to be some refactoring there, to make it easier to
subdivide the /asset virtual folder.
Originally /asset was for classpath assets only. Now I've added
/asset/ctx to context assets.
You will want to assign a virtual pass and a version number, thus:
/asset/fs/1.0/foo/bar.gif should map to <root>/foo/bar.gif.
As with context assets, we should be assigning far-future expires
headers, and supporting gzip.
Do we need to support multiple roots? i.e.
/asset/fs/root1/1.0/foo/bar.gif ... root1 would be mapped to a folder
on the file system, but configuration could map root2 to somewhere
else on the file system entirely.
On Mon, Feb 9, 2009 at 4:20 PM, manuel aldana <al...@gmx.de> wrote:
> Hi Howard,
>
> would like to patch this issue, if you're not working on it:
> https://issues.apache.org/jira/browse/TAP5-423
>
> What do you think about the implementation approach to differ between asset
> types through asset-prefix (e.g. asset-classpath, asset-filesystem). I
> couldn't think of a better way...
>
> After providing filesystem asset, asset types could even be extended
> (database assets, static-resource servers). Especially getting static
> content from special static-content servers is a very common use case for
> bigger sites.
>
>
> --
> manuel aldana
> aldana@gmx.de
> software-engineering blog: http://www.aldana-online.de
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: patching ticket TAP5-423
Posted by manuel aldana <al...@gmx.de>.
I copy/pasted your comment to jira ticket and added my comment to it.
Howard Lewis Ship schrieb:
> Have you thought through the implications of exposing the file system?
> Seems like you would need some configuration to support a root
> directory (which you wouldn't want to be "/").
>
> I think, after that, it would tend to follow the lead of the
> ContextAssetFactory and the related AssetDispatcher code.
>
> Perhaps there needs to be some refactoring there, to make it easier to
> subdivide the /asset virtual folder.
>
> Originally /asset was for classpath assets only. Now I've added
> /asset/ctx to context assets.
>
> You will want to assign a virtual pass and a version number, thus:
>
> /asset/fs/1.0/foo/bar.gif should map to <root>/foo/bar.gif.
>
> As with context assets, we should be assigning far-future expires
> headers, and supporting gzip.
>
> Do we need to support multiple roots? i.e.
> /asset/fs/root1/1.0/foo/bar.gif ... root1 would be mapped to a folder
> on the file system, but configuration could map root2 to somewhere
> else on the file system entirely.
>
>
>
> On Mon, Feb 9, 2009 at 4:20 PM, manuel aldana <al...@gmx.de> wrote:
>
>> Hi Howard,
>>
>> would like to patch this issue, if you're not working on it:
>> https://issues.apache.org/jira/browse/TAP5-423
>>
>> What do you think about the implementation approach to differ between asset
>> types through asset-prefix (e.g. asset-classpath, asset-filesystem). I
>> couldn't think of a better way...
>>
>> After providing filesystem asset, asset types could even be extended
>> (database assets, static-resource servers). Especially getting static
>> content from special static-content servers is a very common use case for
>> bigger sites.
>>
>>
>> --
>> manuel aldana
>> aldana@gmx.de
>> software-engineering blog: http://www.aldana-online.de
>>
>>
>>
>
>
>
>
--
manuel aldana
aldana@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org