commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Gorylenko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (VFS-266) AbstractFileName and AbstractFileObject serialization
Date Fri, 18 Dec 2009 14:03:18 GMT

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

Nikolay Gorylenko commented on VFS-266:
---------------------------------------

Is there any estimate or roadmap for Commons-VFS 2.0 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.0
>
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message