You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Philipp Brügger (JIRA)" <ji...@apache.org> on 2015/04/14 14:56:12 UTC

[jira] [Commented] (VFS-266) AbstractFileName and AbstractFileObject serialization

    [ https://issues.apache.org/jira/browse/VFS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494063#comment-14494063 ] 

Philipp Brügger commented on VFS-266:
-------------------------------------

This is feature from 2009 and seems to be quite outdated. It wasn't release for VFS-2.0 and is now on the never ending roadmap for VFS-2.1. Please remove this thicket from the 2.1 version and recheck again for a future release.

> 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
>             Fix For: 2.1
>
>         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)