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

[JIRA]

[ 
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)

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

[sebb]

On 18/12/2009, Gawie Kellerman  wrote:
> Hi guys...
>
>  Sorry to bother, but I in a moment of weekness subscribed to a whole lot of
>  apache mailing lists.  How do I unsubscribe (know what I am still subscribed
>  to).  It is quite daunting from the mails to actually understand where/what
>  to unsubscribe from.

Just look at the mail header, it includes the following:

List-Help: 
List-Unsubscribe: 
List-Post: 
List-Id: 

The welcome message for each list should also have included
unsubscribe instructions ...

>
>  Regards and Thanks,
>  Gawie

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

[Gawie Kellerman]

Hi guys...

Sorry to bother, but I in a moment of weekness subscribed to a whole lot of
apache mailing lists.  How do I unsubscribe (know what I am still subscribed
to).  It is quite daunting from the mails to actually understand where/what
to unsubscribe from.

Regards and Thanks,
Gawie

On Fri, Dec 18, 2009 at 4:03 PM, Nikolay Gorylenko (JIRA)
wrote:

>
>[
> 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.
>
>

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

[Nikolay Gorylenko (JIRA)]

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

Nikolay Gorylenko commented on VFS-266:
---

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.

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

[Nikolay Gorylenko (JIRA)]

[ 
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.

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

[Vince Bonfanti (JIRA)]

[ 
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.