http://www.eclipse.org/platform: File Buffers (Eclipse Foundation) 
Copyright (c) 2000, 2009 IBM Corporation and others.
This program and the accompanying materials
are made available under the terms of the Eclipse Public License 2.0
which accompanies this distribution, and is available at
https://www.eclipse.org/legal/epl-2.0/
SPDX-License-Identifier: EPL-2.0
Contributors:
    IBM Corporation - initial API and implementation

/*******************************************************************************
 * Copyright (c) 2000, 2009 IBM Corporation and others.
 *
 * This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License 2.0
 * which accompanies this distribution, and is available at
 * https://www.eclipse.org/legal/epl-2.0/
 *
 * SPDX-License-Identifier: EPL-2.0
 *
 * Contributors:
 *     IBM Corporation - initial API and implementation
 *******************************************************************************/
package org.eclipse.core.filebuffers;


A file buffer manager (see IFileBufferManager) uses an ISynchronizationContext in order to execute commands encapsulated as Runnable. The synchronization context executes the Runnables
according to a specific synchronization/execution policy. This could be that the given
Runnable is executed in a specific thread or environment or adhere to specific
timing constraints. The concrete characteristics of the policy is to be specified by the context
implementer.

 This interface can be implemented by clients. Clients use IFileBufferManager.setSynchronizationContext(ISynchronizationContext) to install a particular synchronization context with a file buffer manager. 
Since:3.0
/**
 * A file buffer manager (see {@link org.eclipse.core.filebuffers.IFileBufferManager}) uses an
 * <code>ISynchronizationContext</code> in order to execute commands encapsulated as
 * {@link java.lang.Runnable}. The synchronization context executes the <code>Runnables</code>
 * according to a specific synchronization/execution policy. This could be that the given
 * <code>Runnable</code> is executed in a specific thread or environment or adhere to specific
 * timing constraints. The concrete characteristics of the policy is to be specified by the context
 * implementer.
 * <p>
 * This interface can be implemented by clients. Clients use
 * {@link org.eclipse.core.filebuffers.IFileBufferManager#setSynchronizationContext(ISynchronizationContext)}
 * to install a particular synchronization context with a file buffer manager.
 *
 * @since 3.0
 */
public interface ISynchronizationContext {

	
Executes the given runnable according to the specified
synchronization/execution policy.

Params:
  • runnable – the runnable to be executed
/**
	 * Executes the given runnable according to the specified
	 * synchronization/execution policy.
	 *
	 *
	 * @param runnable the runnable to be executed
	 */
	void run(Runnable runnable);
}