As with most things I post here, you probably don't need to know the details to get by, but it sure helps to understand them. Case in point...
As part of some behind the scenes "figuring stuff out so we can tell the client how it works", I happened to ping the Function1 guys (some ex-BID consulting folks) about the IDK. What I was trying to figure out was how the IDK PRC actually talked to Collaboration/Publisher. It didn't take long for them to come up with an answer. Here's a blog post on what they found.
Interestingly enough, the PRC goes directly to the Collaboration and Publisher hosts, completely bypassing the API server (after an initial call).
Update:
As per the always informative Gerald Kanapahty comments on my blog: the base URL for the Publisher and Collaboration web services actually come from the portal itself. The IDK looks up the UUID of the Publisher/Collaboration remote server objects in portal administration and uses those base URL's to build the full web service URI's.
Definitely a great analysis, guys (and thanks for plugging my blog).
Leave a comment