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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,86adf9f3441b35ad X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nntp.club.cc.cmu.edu!feeder.erje.net!news2.arglkargh.de!noris.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: requeue vs requeue with abort - code example pleaseeee Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <7bd3db89-ae9d-4e09-9590-676f85dcef9a@w2g2000yqb.googlegroups.com> Date: Thu, 9 Dec 2010 17:22:55 +0100 Message-ID: NNTP-Posting-Date: 09 Dec 2010 17:22:55 CET NNTP-Posting-Host: 0357546c.newsspool3.arcor-online.net X-Trace: DXC=LY]ji0DkdGcJ00P1S40fZgMcF=Q^Z^V3h4Fo<]lROoRa8kFOW4edINk[6LHn;2LCVn7enW;^6ZC`d\`mfM[68DCc2JO1TXSg^@k X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:15868 Date: 2010-12-09T17:22:55+01:00 List-Id: On Thu, 9 Dec 2010 05:57:09 -0800 (PST), domel wrote: > Since few weeks I'm learning ADA. I got stuck on requeue facility. I > canno't completely grasp what the difference between requeue and > requeue with abort is. Use "requeue with abort" when the request is cancelable, i.e. serving it in its current entry has not changed anything that could get broken if the request were canceled later. This is the desired behavior. If serving the request changes some vital things, e.g. you have initiated its for processing memorizing some things etc, then use "requeue." Don't do this if you don't need to, because it would make the clients blocked until the request is serviced (a timed entry will not be able to cancel it). -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de