ISync.cs :  » Inversion-of-Control-Dependency-Injection » Spring.net » Spring » Threading » C# / CSharp Open Source

Home
C# / CSharp Open Source
1.2.6.4 mono .net core
2.2.6.4 mono core
3.Aspect Oriented Frameworks
4.Bloggers
5.Build Systems
6.Business Application
7.Charting Reporting Tools
8.Chat Servers
9.Code Coverage Tools
10.Content Management Systems CMS
11.CRM ERP
12.Database
13.Development
14.Email
15.Forum
16.Game
17.GIS
18.GUI
19.IDEs
20.Installers Generators
21.Inversion of Control Dependency Injection
22.Issue Tracking
23.Logging Tools
24.Message
25.Mobile
26.Network Clients
27.Network Servers
28.Office
29.PDF
30.Persistence Frameworks
31.Portals
32.Profilers
33.Project Management
34.RSS RDF
35.Rule Engines
36.Script
37.Search Engines
38.Sound Audio
39.Source Control
40.SQL Clients
41.Template Engines
42.Testing
43.UML
44.Web Frameworks
45.Web Service
46.Web Testing
47.Wiki Engines
48.Windows Presentation Foundation
49.Workflows
50.XML Parsers
C# / C Sharp
C# / C Sharp by API
C# / CSharp Tutorial
C# / CSharp Open Source » Inversion of Control Dependency Injection » Spring.net 
Spring.net » Spring » Threading » ISync.cs
#region License
/*
* Copyright  2002-2005 the original author or authors.
* 
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
* 
*      http://www.apache.org/licenses/LICENSE-2.0
* 
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#endregion

namespace Spring.Threading{
    /// <summary>
    /// Acquire/Release protocol, base of many concurrency utilities.
    /// </summary>
    /// 
    /// <remarks>
    /// <p><see cref="ISync"/> objects isolate waiting and notification for particular logical 
    /// states, resource availability, events, and the like that are shared 
    /// across multiple threads.</p>
    /// 
    /// <p>Use of <see cref="ISync"/>s sometimes (but by no means always) adds 
    /// flexibility and efficiency compared to the use of plain 
    /// .Net monitor methods and locking, and are sometimes (but by no means 
    /// always) simpler to program with.</p>
    /// 
    /// <p>Used for implementation of a <see cref="Spring.Pool.Support.SimplePool"/></p>
    /// </remarks>
    /// 
    /// <author>Doug Lea</author>
    /// <author>Federico Spinazzi (.Net)</author>
    public interface ISync
  {
        /// <summary>  Wait (possibly forever) until successful passage.
        /// Fail only upon interuption. Interruptions always result in
        /// `clean' failures. On failure,  you can be sure that it has not 
        /// been acquired, and that no 
        /// corresponding release should be performed. Conversely,
        /// a normal return guarantees that the acquire was successful.
        /// 
        /// </summary>
        void Acquire();

        /// <summary> Potentially enable others to pass.
        /// <p>
        /// Because release does not raise exceptions, 
        /// it can be used in `finally' clauses without requiring extra
        /// embedded try/catch blocks. But keep in mind that
        /// as with any java method, implementations may 
        /// still throw unchecked exceptions such as Error or NullPointerException
        /// when faced with uncontinuable errors. However, these should normally
        /// only be caught by higher-level error handlers.
        /// </p>
        /// </summary>
        void Release ();
        
        /// <summary>
        /// Wait at most msecs to pass; report whether passed. 
        /// <p>
        /// The method has best-effort semantics:
        /// The msecs bound cannot
        /// be guaranteed to be a precise upper bound on wait time in Java.
        /// Implementations generally can only attempt to return as soon as possible
        /// after the specified bound. Also, timers in Java do not stop during garbage
        /// collection, so timeouts can occur just because a GC intervened.
        /// So, msecs arguments should be used in
        /// a coarse-grained manner. Further,
        /// implementations cannot always guarantee that this method
        /// will return at all without blocking indefinitely when used in
        /// unintended ways. For example, deadlocks may be encountered
        /// when called in an unintended context.
        /// </p>
        /// </summary>
        /// <param name="msecs">the number of milleseconds to wait
        /// An argument less than or equal to zero means not to wait at all. 
        /// However, this may still require
        /// access to a synchronization lock, which can impose unbounded
        /// delay if there is a lot of contention among threads.
        /// </param>
        /// <returns>true if acquired</returns>
        bool Attempt(long msecs);
    }
}
www.java2v.com | Contact Us
Copyright 2009 - 12 Demo Source and Support. All rights reserved.
All other trademarks are property of their respective owners.