Hello Thomas,
> OK, my mistake then. I though the JavaHL and JavaSVN where
> API's on top of a protocol only and that only the server side
> was concerned with FSFS. Just out of curiosity, why is the
> client concerned with that?
In order to support local access over "file" protocol.
Alexander Kitaev,
TMate Software,
http://tmate.org/
> -----Original Message-----
> From: Thomas Hallgren [mailto:thomas@tada.se]
> Sent: Thursday, July 06, 2006 1:50 PM
> To: dev@subclipse.tigris.org
> Subject: Re: [Subclipse-dev] Submitting Subclipse as project
> to Eclipse.org
>
> Brock Janiczak wrote:
> > Eclipse already uses natives for things other than SWT, for
> instance
> > the filesystem plugin.
>
> The filesystem platform native plugin is optional and only
> needed when you want automatic workspace refresh (since Java
> has no API for file system events ... yet). I assure you, we
> really do create platform agnostic distributions based on Eclipse.
>
> > The short answer is: "very hard". You would need to
> support the SVN
> > working copy format (not so hard) as well as the FSFS
> repository type
> > (really hard). Maintenance would be a major issue. The Subversion
> > team does a great job of adding new features, which is great for
> > users, but not so great if you have to maintain your own
> client implementation.
>
> OK, my mistake then. I though the JavaHL and JavaSVN where
> API's on top of a protocol only and that only the server side
> was concerned with FSFS. Just out of curiosity, why is the
> client concerned with that?
>
> Regards,
> Thomas Hallgren
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Jul 6 12:00:13 2006