Re: [Subclipse-dev] Revision graph and cache implementation

I agree that we should stay away from serialization.

As you experiment with the cache implementation you might want to take the
opportunity to do whatever refactoring is necessary to decouple the caching
implementation from the UI as much as possible so it will be easier to snap
in a different implementation should a better one come up. For example, the
database-related stuff could come out of the editor, and maybe there should
be an ICache interface so that the cache implementation could be changed
without touching the editor.

On 7/8/08 8:32 AM, "Mark Phippard" <markphip_at_gmail.com> wrote:

> Doesn't serialization open the door to memory problems? If I have a
> massive cache and you want to read it all into memory it seems like
> that would be a problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-07-08 17:47:50 CEST