User-Id is one of the properties returned by the ZAP handler and stored as meta-data. It's got its own field in the ZAP message structure because we could be doing access control at the lower level, based on user IDs returned after authentication. (For libzmq to do that would require more extensions.)
On Thu, Jun 26, 2014 at 11:06 AM, Peter Kleiweg <[email protected]> wrote: > > I wrote some code in Go to deal with metadata. Here is an > example of how to use it: > > http://godoc.org/github.com/pebbe/zmq4#example-AuthStart > > This makes the most sense to me. Any suggestions? > > Am I right to assume that when you send a multi-part message to > a socket with authentication (or is it authorisation?), then > each frame gets the same metadata attached? So I can read it > from the first frame, and don't have to bother with metadata > from the other frames? > > Some other questions: > > What are standard metadata properties? > User-Id, Socket-Type, any others? > > Why is User-Id set separately, instead of as just one of the > other metadata-properties? Historical error? > > > -- > Peter Kleiweg > http://pkleiweg.home.xs4all.nl/ > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
