Re^2: how to handle comparison of binary type attributes in LDAP

It's comparing LDAP entries from two servers. It could be a comparison between Primary and secondary or two LDAP server in different environment, e.g: DEV,QA,PROD. I got this written already, but as I analyze the result I noticed the Binary type is throwing me off track when I do a comparison. Hence I thought I could avoid by just doing length equality comparison on the value. BTW, what is an XY problem?

Comment on Re^2: how to handle comparison of binary type attributes in LDAP

Replies are listed 'Best First'.
Re^3: how to handle comparison of binary type attributes in LDAP by idsfa (Vicar) on Feb 21, 2007 at 03:56 UTC
(Read the link in my earlier post for several good explanations of the XY problem) Comparing the length only doesn't help if , for example, your binary data is a set of bit flags ... the value is important, too. I'd recommend MIME::Base64 encoding each value before comparing (neatly sidestepping the question of whether or not the original was binary). The intelligent reader will judge for himself. Without examining the facts fully and fairly, there is no way of knowing whether vox populi is really vox dei, or merely vox asinorum. — Cyrus H. Gordon	[reply]

Replies are listed 'Best First'.

Re^3: how to handle comparison of binary type attributes in LDAP
by idsfa (Vicar) on Feb 21, 2007 at 03:56 UTC

(Read the link in my earlier post for several good explanations of the XY problem)

Comparing the length only doesn't help if , for example, your binary data is a set of bit flags ... the value is important, too. I'd recommend MIME::Base64 encoding each value before comparing (neatly sidestepping the question of whether or not the original was binary).

The intelligent reader will judge for himself. Without examining the facts fully and fairly, there is no way of knowing whether vox populi is really vox dei, or merely vox asinorum. — Cyrus H. Gordon

[reply]