From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,af960bc705aaf51b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-02-28 15:38:18 PST From: Dale Stanbrough Newsgroups: comp.lang.ada Subject: Re: Complexity of protected objects Organization: RMIT References: <3C7A75F2.30503@worldnet.att.net> <3c7e7c60.8192226@news.cis.dfn.de> User-Agent: MT-NewsWatcher/3.2 (PPC Mac OS X) Date: Fri, 01 Mar 2002 10:32:42 +1100 Message-ID: NNTP-Posting-Host: dale.cs.rmit.edu.au X-Trace: itsawnews.its.rmit.edu.au 1014939331 dale.cs.rmit.edu.au (1 Mar 2002 10:35:31 +1100) Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.maxwell.syr.edu!news.mel.connect.com.au!newshub1.rdc1.nsw.optushome.com.au!harbinger.cc.monash.edu.au!vrn.edu.au!131.170.8.40.MISMATCH!itsawnews.its.rmit.edu.au!dale Xref: archiver1.google.com comp.lang.ada:20615 Date: 2002-03-01T10:32:42+11:00 List-Id: Jim Rogers wrote: > Using a protected object to read and write files is a clear >violation of the intention and recommendations for proctected >objects. Protected objects should be non-blocking. I/O is >always potentially blocking. Why is this? I see this as being a piece of programming advice, - it's not a good idea to hold locks for a long time - but is there any more to it than that? Are there some other consequences of scheduling than that? Dale ------------ And now a word from our sponsor ------------------ Do your users want the best web-email gateway? Don't let your customers drift off to free webmail services install your own web gateway! -- See http://netwinsite.com/sponsor/sponsor_webmail.htm ----