Re: [uddi-spec] Use of maxRows and listHead in V3

["Mirek Novotny" <mirek.novotny@systinet.com>]

I would rather use E_unsupported fro such cases as E_fatalError IMHO should be reserved for unexpected system failures (like lost connection to database etc.)  In this case it might be expected that someone tries to send such value and implementation should reflect that.

 

The only trouble is that the description in spec is probably more about missing implementation of existing feature.

 E_unsupported: (10050) Signifies that the implementer does not support a feature or API.

 

Any thouhgts?

 

Mirek

----- Original Message -----

From: Daniel Feygin

To: 'Rogers, Tony' ; uddi-spec@lists.oasis-open.org

Cc: 'Andrew Hately'

Sent: Sunday, August 15, 2004 6:38 PM

Subject: RE: [uddi-spec] Use of maxRows and listHead in V3

Ok, maxRows=0 is useful indeed.

 

For negative numbers the only error code that seems to make sense is E_fatalError.

 

Daniel

---

From: Rogers, Tony [mailto:Tony.Rogers@ca.com]
Sent: Friday, August 13, 2004 2:57 AM
To: Daniel Feygin
Cc: uddi-spec@lists.oasis-open.org; Andrew Hately
Subject: RE: [uddi-spec] Use of maxRows and listHead in V3

If we return no results on maxrows = 0, but return the number of results, then the program can use that number to prepare for a second call to receive the results - that's the usual rationale for including a "return 0 results but tell me how many there are" call. It's less useful for these results, because they vary in size, but that is what I'd see it being used for. That, or some statistical analysis application, where they are interested in the number of results rather than the content.

 

Anyway, it seemed to me that there was some (albeit small) use for accepting maxRows=0.

 

As for negative numbers - you have a point - maybe we should reject the request. Would you care to suggest a suitable error?

 

Tony Rogers

tony.rogers@ca.com