-
sleep or yield?
javadoc indicates that thread.sleep will not cause a loss of ownership of
any monitor.
Yield will cause a currently executing thread to pause and allow other threads
to execute.
What would be better to use when implementing a one thread to monitor another?
Or should I just set the monitoring thread's priority lower than the executing
thread?
Rob
-
Re: sleep or yield?
Instead of all that , u can use
shared data that will change reflecting the status of one thread.
Or u can go for mutual reccrsion which calls mathod of
each other infoming the status of each each.
-Ashish patel
"Rob" <rstauder@esri.com> wrote:
>
>javadoc indicates that thread.sleep will not cause a loss of ownership of
>any monitor.
>
>Yield will cause a currently executing thread to pause and allow other threads
>to execute.
>
>What would be better to use when implementing a one thread to monitor another?
> Or should I just set the monitoring thread's priority lower than the executing
>thread?
>
>Rob
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
|
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL
|
Bookmarks