[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711140#action_12711140
]
Mark Yvanovich commented on TRINIDAD-1464:
--
Rather than nesting the config
[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711142#action_12711142
]
Matthias Weßendorf commented on TRINIDAD-1464:
--
I had a grouping in mind to
[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12706769#action_12706769
]
Matthias Weßendorf commented on TRINIDAD-1464:
--
Another approach is using
follow up on the suggested EL scheme approach:
Using EL scheme inside the trinidad config:
By that the application EL binds the trinidad-config (new) attributes.
On each request the (current) implementation of the UploadProcessor
rereads the EL-bound attributes. Therefore the application is free
Matthias Wessendorf said the following On 5/5/2009 10:01 PM PT:
Hi Blake,
the idea is to change the upload-config during runtime.
Not sure how moving it to trinidad-config helps to change it
via an Java API.
-Matthias
My thinking was that the application EL binds the trinidad-config
My thinking was that the application EL binds the trinidad-config
attribute. Since we reread the EL-bound attributes on each request, the
application is free to use any scheme it wants to determine the maximum
size, including doing so on a per-user or per-user-per-request basis.
oh yeah.
Hi Blake,
the idea is to change the upload-config during runtime.
Not sure how moving it to trinidad-config helps to change it
via an Java API.
-Matthias
On Fri, May 1, 2009 at 7:18 PM, Blake Sullivan
blake.sulli...@oracle.com wrote:
Matthias,
Would things be improved if we moved the
[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12704962#action_12704962
]
Matthias Weßendorf commented on TRINIDAD-1464:
--
One possible approach:
[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12704963#action_12704963
]
Matthias Weßendorf commented on TRINIDAD-1464:
--
Generally, the problem is
Matthias,
Would things be improved if we moved the configuration to
trinidad-config.xml and allowed the configuration to be retrieved on a
per-request basis?
-- Blake Sullivan
Matthias Weßendorf (JIRA) said the following On 5/1/2009 4:25 AM PT:
[
[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12704509#action_12704509
]
Matthias Weßendorf commented on TRINIDAD-1464:
--
The most simple case would
11 matches
Mail list logo