[
https://issues.apache.org/jira/browse/VFS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738996#action_12738996
]
Vince Bonfanti commented on VFS-266:
------------------------------------
I've reworked the caching implementation for the GaeVFS plug-in to no longer
require this serialization code. However, the patch has been tested and the
changes are relatively minor, so it might be desirable to apply this patch
anyway, in case anyone ever needs to serialize the AbstractFileName and
AbstractFileObject classes for any other reason in the future.
> 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.
