From roby Thu Jun 20 14:45:35 1996 Return-Path: Date: Thu, 20 Jun 96 14:45:34 EDT From: roby (Clyde Roby) To: SBlake@ThomSoft.Com Subject: "tasking safe" interfaces in ASIS? Cc: roby, ASIS-Officers@SW-Eng.Falls-Church.Va.US Content-Length: 569 X-Lines: 16 Status: OR Steve, One other issue raised at the WG9 meeting was the "tasking safeness" of the interfaces within ASIS. That is, can there be two separate threads of control through ASIS (any particular ASIS query or ASIS interface) so that nothing is messed up -- each control thread runs okay. A possible place where this may not currently exist (after a cursory glance through the spec by Erhard) would be the error handling interfaces, especially retrieving the information that caused the most recent error. All the interfaces within ASIS must be "tasking safe". Clyde From cooper@longshot.ds.boeing.com Thu Jun 20 18:10:24 1996 Return-Path: Date: Thu, 20 Jun 1996 14:54:53 -0700 From: cooper@longshot.ds.boeing.com (Dan Cooper) To: ASIS-officers@sw-eng.falls-church.va.us Subject: Re: "tasking safe" interfaces in ASIS? Content-Length: 249 X-Lines: 9 Status: OR Clyde writes, > All the interfaces within ASIS must be "tasking safe". Sounds like a requirement to me. Do we have a list of such requirements someplace (like we do for "design goals")? Or maybe this is a design goal? A new issue? --Dan Cooper From roby Fri Jun 21 15:33:53 1996 Return-Path: Date: Fri, 21 Jun 96 15:33:52 EDT From: roby (Clyde Roby) To: cooper@longshot.ds.boeing.com Subject: Re: "tasking safe" interfaces in ASIS? Cc: roby, ASIS-Officers@SW-Eng.Falls-Church.Va.US Content-Length: 398 X-Lines: 14 Status: OR Dan and all, > Clyde writes, > > > All the interfaces within ASIS must be "tasking safe". > > Sounds like a requirement to me. Do we have a list of such requirements > someplace (like we do for "design goals")? Or maybe this is a design > goal? A new issue? I think that we should go ahead and make it a new Issue, "ASIS must be tasking-safe". I'll add it to the Issues-Summary list. Clyde From colket@smtp-gw.spawar.navy.mil Thu Jun 27 08:33:16 1996 Return-Path: Date: Thu, 27 Jun 1996 08:15:55 -0400 From: colket@smtp-gw.spawar.navy.mil (Currie Colket) Subject: Re[2]: "tasking safe" interfaces in ASIS? To: cooper@longshot.ds.boeing.com, roby@ida.org (Clyde Roby) Cc: roby@ida.org, ASIS-Officers@sw-eng.falls-church.va.us Content-Type: text/plain; charset=US-ASCII Content-Description: cc:Mail note part Content-Length: 993 X-Lines: 34 Status: OR Clyde, Dan, and All, The request from WG9 was not necessarily to make ASIS tasking safe. Their request was to have a section in the specification that addressed tasking safeness. If at all possible they would like ASIS to be tasking safe and if possible, we should do so, but this is NOT the requirement. Yes, this should be included as an issue to the issue summary list. v/r Currie ______________________________ Reply Separator _________________________________ Subject: Re: "tasking safe" interfaces in ASIS? Author: roby@ida.org (Clyde Roby) at SMTP-GW Date: 6/21/96 3:33 PM Dan and all, > Clyde writes, > > > All the interfaces within ASIS must be "tasking safe". > > Sounds like a requirement to me. Do we have a list of such requirements > someplace (like we do for "design goals")? Or maybe this is a design > goal? A new issue? I think that we should go ahead and make it a new Issue, "ASIS must be tasking-safe". I'll add it to the Issues-Summary list. Clyde