You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Bernd Eckenfels (JIRA)" <ji...@apache.org> on 2015/04/14 15:12:12 UTC
[jira] [Updated] (VFS-266) AbstractFileName and AbstractFileObject
serialization
[ https://issues.apache.org/jira/browse/VFS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernd Eckenfels updated VFS-266:
--------------------------------
Fix Version/s: (was: 2.1)
> AbstractFileName and AbstractFileObject serialization
> -----------------------------------------------------
>
> Key: VFS-266
> URL: https://issues.apache.org/jira/browse/VFS-266
> Project: Commons VFS
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Google App Engine Java
> Reporter: Vince Bonfanti
> Attachments: VFS-abstractfilename-abstractfileobject-serialization.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I'm implementing a VFS plug-in that implements a distributed, writeable file system for Google App Engine (GAE) Java (see gaevfs.appspot.com for more info). In order for this to work properly, I need to create a distributed FilesCache implementation using the memcache API provided by GAE. However, memcache requires that both keys and values must be serializable. Therefore, to complete my implementation, I need to make AbstractFileName and AbstractFileObject serializable (because my implementation classes inherit from these).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)