[jira] Commented: (TAP5-423) Implement a file-system Asset type

["manuel aldana (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672088#action_12672088 ] 

manuel aldana commented on TAP5-423:
------------------------------------

Comment by Howard (copy/paste maillist):

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.


> Implement a file-system Asset type
> ----------------------------------
>
>                 Key: TAP5-423
>                 URL: https://issues.apache.org/jira/browse/TAP5-423
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: manuel aldana
>
> currenty it is built in to retrieve assets from classpath and from webcontext.
> a file system asset type which can retrieve stuff directly from the filesystem (e.g. from /srv/statics/xxxx) makes also sense. 
> something like:
> *ResourceFileSystem extends AbstractResource* and *FileSystemAssetFactory extends AssetFactory*

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.