A webserver framework which addresses both formal and informal (machine and meat) users, can deduplicate efforts by, (A) always sending the formal Response, and then for informality add an extra script that deformalises a corresponding interface for meat use. But this is a formality-oriented design decision, which is more machine-oriented, and contrary to lay-human intuition. A meat-oriented design, conversely, would (B) always send the informal Response, but only send a formal Response upon escalation.
All that being said, it seems that pre-emptive deduplication is going to be a poor design pattern, overall. Instead, (C) there should be different Request parameters demanding either formal/machine, or informal/meat, Responses. Responses-formality should therefore, be specific to the Requested-formality. And finally always, a Response must include the hyperlink which sends the same Response but parameterized for alternative degrees of formality.
#hci #restful #www #hateoas
( In case you have no idea what I just wrote above, here is some context. )
No comments :
Post a Comment