[MGNLUI-3775] Design a dedicated component to handle temporary files lifecycle Created: 16/Feb/16 Updated: 10/Mar/17 Resolved: 10/Mar/17 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.4.4 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Date of First Response: | |||||||||||||
| Story Points: | 13 | ||||||||||||
| Description |
|
Attempts to solve issues related to clean-up of temporary files produced by form fields ( One possible solution to this problem is to abstract from the actual specific type of the UIContext:
|
| Comments |
| Comment by Mikaël Geljić [ 09/Mar/17 ] |
|
Was for temp upload files, but seems no-one complains about whatever solution we have for it at the moment (be it scheduled or on subapp close). That said, my gut feelings tell me the servlet container should take care of that, not us. |
| Comment by Michael Mühlebach [ 10/Mar/17 ] |
|
Well, knowing our code ... not closing things is our thing But if I understood you correctly we don't need it atm or maybe not even at all? |
| Comment by Mikaël Geljić [ 10/Mar/17 ] |
|
Unless proven otherwise, correct. |