[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [provision] async lookup?
Right. So do we have consensus that: - Lookup maybe sunc/async - ListTargets is sync only Darran Gary P Cole wrote: > Sure. It's a chicken-and-egg thing--a conundrum. 1) It doesn't make > sense for a requestor to specify asynchronous execution for a > listTargets operation asynchronously because the requestor cannot know > whether the provider supports asynchronous execution until AFTER the > requestor has examined the set of capabilities that each target supports. > 2) It doesn't make sense for a provider to choose asynchronous > execution for a listTargets operation because the requestor will have > no way of knowing whether the provider supports asynchronous execution > (and that the provider therefore might choose to execute a requested > operation asynchronously) until AFTER the requestor has examined the > set of capabilities that each target supports. > > Cohen, Doron wrote: > >> Gary, >> >> 2) I do not see why listTargets can not be async. Can you remind me >> what was >> the reason brought up for this ? >> >> Doron >> >> -----Original Message----- >> From: Gary P Cole [mailto:Gary.P.Cole@Sun.COM] Sent: Tuesday, >> November 16, 2004 3:38 PM >> To: Cohen, Doron; Gearard Woods >> Cc: PSTC >> Subject: Re: [provision] async lookup? >> >> Fair enough. 1) Gerry, do you agree that lookup can be async? >> 2) Doron, do you agree that listTargets must be sync? >> >> Cohen, Doron wrote: >> >> >> >>> Gary, >>> >>> I do not see a reason why lookup must be sync. In fact, if the PSP is >>> providing async capability, I do not see why it should not provide >>> it for >>> lookup. >>> Doron >>> >>> -----Original Message----- >>> From: Gary P Cole [mailto:Gary.P.Cole@Sun.COM] Sent: Tuesday, >>> November 16, 2004 12:03 AM >>> To: Gary P Cole >>> Cc: Gearard Woods; PSTC >>> Subject: [provision] async lookup? >>> >>> Should a 'lookup' be executed asynchronously? Or should we state >>> that a 'lookup' must be synchronous? >>> >>> The last time we hashed over sync/async, Doron said that any >>> operation could be asynchronous unless there was a specific reason >>> to preclude async execution. We've so far established specific >>> reasons why 'status', 'cancel', and 'listTargets' must be synchronous. >>> >>> Gary P Cole wrote: >>> >>> >>> >>> >>> >>>> Gearard Woods wrote: >>>> >>>> >>>> >>>> >>>>> 3.4.1.3.1 >>>>> Should lookup allow asychronous operation? >>>>> >>>>> >>>>> >>>> >>>> I cannot imagine wanting an asynchronous lookup, but I didn't feel >>>> certain enough of this to say that it couldn't. Should we float >>>> this one to the list? >>>> >>>> >>> >>> >>> To unsubscribe from this mailing list (and be removed from the >>> roster of >>> >> >> the >> >> >>> OASIS TC), go to >>> http://www.oasis-open.org/apps/org/workgroup/provision/members/leave_workgr >>> >>> >> >> o >> >> >>> up.php. >>> >>> >>> >> >> >> >> > > > > To unsubscribe from this mailing list (and be removed from the roster > of the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/provision/members/leave_workgroup.php. > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]