Draft 8 says this about retrieving endpoint properties:

    7.7.4.1.5. Response
    ....
   
    If the ALTO Server does not define a requested property for a
    particular endpoint, then it MUST omit it from the response
    for only that endpoint.

So if a client asks for a non-existent property type,
wouldn't it be easier just to treat it as 'undefined for
that endpoint', and simply ignore it, rather than requiring
the server to return an E_INVALID_PROPERTY_TYPE error?

It would also be consistent with the filtered network map and
cost map services, because those are supposed to quietly ignore
invalid pids. And it would make a server marginally simpler.

In case you didn't guess, I'm in favor of legislating errors out of
existence, whenever possible.

        - Bill Roome


_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to