Reading the Documentation

[billroper]

One of my specialties at work seems to be reading the Microsoft documentation for MFC, the OS, etc. and then trying to figure out what they actually mean by it. Today's entertainment was a return to the ugly world of RPC, where we were having a problem with requiring a domain trust relationship for authentication even when we thought we weren't using NTLM authentication.

Of course, it turned out that we were using NTLM authentication, we just didn't know it. So I fixed that.

I still don't know why requests with RPC_C_AUTHN_NONE as the authentication service don't trip off the security callback function (and, yes, I did set the RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH flag in the call to RpcServerRegisterIf2). But I've worked around the problem.

Exactly why I'm the expert on this is hard to fathom, save for the fact that I can actually read documentation. From Microsoft.

And all of you who just had your eyes glaze over? It's ok. Just smile and nod. :)

Comments

[tigertoy.livejournal.com]

I find Microsoft's documentation very frustrating. The answer to my question is usually in there somewhere, but it's very hard to find. Even if I already know the name of the feature I want, I often have to poke around following links from the page for the feature for a long time to actually get the answer to my question, and if I don't know the name of the feature, I'm in deep doo-doo.

Of course, I've been working in Java for the last few months, and Sun's Java documentation is no better overall, and in fact probably worse.

[katyhh.livejournal.com]

*smiles and nods* :)
Looking forward to seeing you in a week! Yay!