[Nsi-wg] Query renaming

[Guy Roberts]

John,

Splitting the Query into two parts makes reasonable sense to me since we already half-way there as we have two response types: QuerySummaryResult and QueryDetailedResult.

Guy

-----Original Message-----
From: nsi-wg-bounces at ogf.org [mailto:nsi-wg-bounces at ogf.org] On Behalf Of John MacAuley
Sent: 28 January 2013 13:56
To: nsi-wg at ogf.org Group
Subject: [Nsi-wg] Query renaming

Peoples,

THe agreement out of our last meeting was to introduce the querySynch() command to support a synchronous (blocking) summary query command.  This operation would not support the detailed query behaviours.

To maintain consistency in operation naming, I would like to break the current asynchronous query operation into two separate commands: query() that would provide the asynchronous summary query for the schedule, and queryDetails() that would provide the recursive tree view of the schedule.

query() would have the same parameters and confirmation result type as querySynch().

If people support this change, then I will go ahead and make it at the same time I add the querySynch() operation.

I am open for naming changes as well.  If someone thinks querySummary() and querySummarySynch() are better operation names.

Thank you,
John

_______________________________________________
nsi-wg mailing list
nsi-wg at ogf.org
https://www.ogf.org/mailman/listinfo/nsi-wg