/**
     * Creates and returns an initial context.
     *
     * @return the initial context
     */
    public static InitialContext create() {
        try {
            return new InitialContext();
        } catch (final NamingException ex) {
            throw new NamingRuntimeException(ex);
        }
    }

    /**
     * Creates and returns an initial context using the specified environment.
     *

        }
        INSTANCE = new SingletonContext(p);
    }

    /**
     * Get singleton context
     *
     * The singleton context will use system properties for configuration as well as values specified in a file
     * specified through this <code>jcifs.properties</code> system property.
     *
     * @return a global context, initialized on first call
     */
    public static synchronized final SingletonContext getInstance() {

func (er erasureObjects) newMultipartUpload(ctx context.Context, bucket string, object string, opts ObjectOptions) (*NewMultipartUploadResult, error) {
	if opts.CheckPrecondFn != nil {
		if !opts.NoLock {
			ns := er.NewNSLock(bucket, object)
			lkctx, err := ns.GetLock(ctx, globalOperationTimeout)
			if err != nil {
				return nil, err
			}
			ctx = lkctx.Context()
			defer ns.Unlock(lkctx)
			opts.NoLock = true
		}

import jcifs.Encodable;

/**
 * SMB2 Create Context request interface. This interface defines the contract for
 * context data included in SMB2 Create requests.
 *
 * @author mbechler
 *
 */
public interface CreateContextRequest extends Encodable {

    /**
     * Get the name of this create context.
     * @return context name as byte array
     */
    byte[] getName();

   * a robolectric test.
   *
   * The functionality that will fail without a valid Context is primarily Cookies and URL Domain handling, but
   * may expand in the future.
   */
  fun initialize(applicationContext: Context) {
    if (PlatformRegistry.applicationContext == null) {
      // Make sure we aren't using an Activity or Service Context
      PlatformRegistry.applicationContext = applicationContext.applicationContext
    }
  }

}

// RefreshHandler - refresh the current lock
func (l *lockRESTServer) RefreshHandler(args *dsync.LockArgs) (*dsync.LockResp, *grid.RemoteErr) {
	// Add a timeout similar to what we expect upstream.
	ctx, cancel := context.WithTimeout(context.Background(), dsync.DefaultTimeouts.RefreshCall)
	defer cancel()

	resp := lockRPCRefresh.NewResponse()
	refreshed, err := l.ll.Refresh(ctx, *args)
	if err != nil {
		return l.makeResp(resp, err)
	}

 * project's source root and project's attachment.<br>
 * The plugin manager would pull the context out of the plugin container context, and populate it into the Mojo.
 *
 */
public interface ContextEnabled {
    /**
     * Set a new shared context <code>Map</code> to a mojo before executing it.
     *
     * @param pluginContext a new <code>Map</code>
     */

should have a convention set, so (1) can be treated as a rare case where a value must be provided by a user.

Best practice is to set conventions in a plugin (2). This keeps the underlying object "dumb", so it can be reused in multiple contexts and doesn't contain any special information about how conventions are calculated or what they could be.  In the wild, we've seen some objects set conventions in the object's constructor (3), but this can lead to unexpected assumptions or coupling...

import jcifs.Decodable;

/**
 * SMB2 Create Context response interface. This interface defines the contract for
 * context data returned in SMB2 Create responses.
 *
 * @author mbechler
 *
 */
public interface CreateContextResponse extends Decodable {

    /**
     * Get the name of this create context.
     * @return context name as byte array
     */
    byte[] getName();

func (lm *LRWMutex) lockLoop(ctx context.Context, id, source string, timeout time.Duration, isWriteLock bool) (locked bool) {
	r := rand.New(rand.NewSource(time.Now().UnixNano()))

	retryCtx, cancel := context.WithTimeout(ctx, timeout)
	defer cancel()

	for {
		select {
		case <-retryCtx.Done():
			// Caller context canceled or we timedout,
			// return false anyways for both situations.