Eclipse Community Forums: Eclipse Platform » Refresh Workspace Automatically

Home » Eclipse Projects » Eclipse Platform » Refresh Workspace Automatically - smart or dumb?

Refresh Workspace Automatically - smart or dumb? [message #286621]

Mon, 13 June 2005 17:11

Eclipse User

Originally posted by: bob.objfac.com

A note on a help page inspired this question:

"If this option is turned on then the workspace resources will be
synchronized with their corresponding resources in the file system
automatically.

"Note: This can potentially be a lengthy operation depending on the
number of resources you have in your workspace."

Hmm. Does this mean that the auto-refresh feature is implemented
inefficiently by default? Specifically,

- For platforms that provide notification of resource changes, does the
SDK ship with platform-dependent refreshProviders that take advantage of
it? (If so, which platforms?)

- For platforms that don't notify, does polling take place in the
background and at what intervals? Are the resource locks fine- or
coarse-grained?

I'd be afraid to turn this on without this information. I like to know
where potentially mysterious responsiveness glitches (like the workspace
auto-save) come from.

Bob

Re: Refresh Workspace Automatically - smart or dumb? [message #286671 is a reply to message #286621]

Tue, 14 June 2005 11:41

Eclipse User

Originally posted by: dj_houghton.nospam.ca.ibm.com

Smart! :-)

See the following bug report for the initial plan item from Eclipse 3.0:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36962

Win32 builds ship with a fragment to the org.eclipse.core.resources
plug-in which contains code to take advantage of file-system callbacks.

On all other file systems it defaults to polling behaviour.
(investigation was done into FAM on Linux but we decided against it)

Everything happens in the background. Code is in the
org.eclipse.core.resources plug-in, in the
org.eclipse.core.internal.refresh package if you'd like to take a look.

Bob Foster wrote:
> A note on a help page inspired this question:
>
> "If this option is turned on then the workspace resources will be
> synchronized with their corresponding resources in the file system
> automatically.
>
> "Note: This can potentially be a lengthy operation depending on the
> number of resources you have in your workspace."
>
> Hmm. Does this mean that the auto-refresh feature is implemented
> inefficiently by default? Specifically,
>
> - For platforms that provide notification of resource changes, does the
> SDK ship with platform-dependent refreshProviders that take advantage of
> it? (If so, which platforms?)
>
> - For platforms that don't notify, does polling take place in the
> background and at what intervals? Are the resource locks fine- or
> coarse-grained?
>
> I'd be afraid to turn this on without this information. I like to know
> where potentially mysterious responsiveness glitches (like the workspace
> auto-save) come from.
>
> Bob

Re: Refresh Workspace Automatically - smart or dumb? [message #286676 is a reply to message #286671]

Tue, 14 June 2005 13:58

Eclipse User

Originally posted by: bob.objfac.com

Looks good. Thanks.

Bob

DJ Houghton wrote:
> Smart! :-)
>
> See the following bug report for the initial plan item from Eclipse 3.0:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=36962
>
> Win32 builds ship with a fragment to the org.eclipse.core.resources
> plug-in which contains code to take advantage of file-system callbacks.
>
> On all other file systems it defaults to polling behaviour.
> (investigation was done into FAM on Linux but we decided against it)
>
> Everything happens in the background. Code is in the
> org.eclipse.core.resources plug-in, in the
> org.eclipse.core.internal.refresh package if you'd like to take a look.
>
>
>
> Bob Foster wrote:
>
>> A note on a help page inspired this question:
>>
>> "If this option is turned on then the workspace resources will be
>> synchronized with their corresponding resources in the file system
>> automatically.
>>
>> "Note: This can potentially be a lengthy operation depending on the
>> number of resources you have in your workspace."
>>
>> Hmm. Does this mean that the auto-refresh feature is implemented
>> inefficiently by default? Specifically,
>>
>> - For platforms that provide notification of resource changes, does
>> the SDK ship with platform-dependent refreshProviders that take
>> advantage of it? (If so, which platforms?)
>>
>> - For platforms that don't notify, does polling take place in the
>> background and at what intervals? Are the resource locks fine- or
>> coarse-grained?
>>
>> I'd be afraid to turn this on without this information. I like to know
>> where potentially mysterious responsiveness glitches (like the
>> workspace auto-save) come from.
>>
>> Bob

Re: Refresh Workspace Automatically - smart or dumb? [message #286715 is a reply to message #286671]

Wed, 15 June 2005 12:30

Eclipse User

On Tue, 14 Jun 2005 11:41:01 -0400, DJ Houghton wrote:
[...]
> On all other file systems it defaults to polling behaviour.
> (investigation was done into FAM on Linux but we decided against it)

Do you have any references to the discussion about this? I'm
interested in reading about the tradeoffs pertaining to FAM.

--
Python is executable pseudocode. Perl is executable line noise.

www: http://dman13.dyndns.org/~dman/ jabber: dman@dman13.dyndns.org

Previous Topic:	Trouble Starting Eclipse 3.0
Next Topic:	plugin status stay in [Installed]

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 04:33:14 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter