Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <653666015.1261144998409.JavaMail.jira@brutus>
Date: Fri, 18 Dec 2009 14:03:18 +0000 (UTC)
From: "Nikolay Gorylenko (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (VFS-266) AbstractFileName and AbstractFileObject
 serialization
In-Reply-To: <348950774.1245702067342.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/VFS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikolay Gorylenko updated VFS-266:
----------------------------------

    Comment: was deleted

(was: Are there any estimations for Commons-VSF 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.