[Mailman-Developers] Architecture for extra profile info

Stephen J. Turnbull stephen at xemacs.org
Sat Apr 27 17:36:33 CEST 2013


Richard Wackerbarth writes:

 > Primary Key == An identifier of the server's choice that identifies
 > a unique instance of the specified resource.  It is important to
 > note that the client CANNOT rely on any particular scheme for
 > mapping other keys to this identifier.

That's true for resources that were added after the client was
written, but there's no reason I can see why we shouldn't make it easy
for people to write URIs by hand if they know something about Mailman.

 > > These URIs are pretty ugly.  Surely we can do better?
 > 
 > Perhaps we can. But we need to conform to the HAL framework style.

Well, I haven't studied it carefully, but the examples on Mike Kelly's
pages are pretty enough.

 > As I understand it, the consumer understands the semantics of
 > various links, but the actual links are "discovered" as a part of
 > previous queries and not "constructed".  As such, the links depend
 > more on the ease of implementation rather than their "beauty".

>From the consumer's point of view, yes, the links are discovered.  But
the producer constructs them.



More information about the Mailman-Developers mailing list