I'd stick with only one: eznode, as two ids is a wee bit too more for most users.
eznode because that the one they can see (eg in the admin interface, the title on the links -tooltip- contains the node id).
Moreover, you never display an object on a full view, but the main node containing this object, isn't it ? So that's more logical as well to only deal with the node id for the users.
Thanks for this, I have been using Node but it is interesting that they would use the two.. It would be great for eZ to give some examples where you would use each. Otherwise we are likely to come across systems in the future where the users has picked eznode and ezobject at random.
Tony
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
I'm not entirely sure, but it would seem to me that there's a remote possibility, that a node would point to another object over time whereas the contentobject id truly is static for an object?
The only difference I can think of is that eznode:// will point to a particular node (objects can have many) where ezobject:// will always point to the main node associated with the object.
So eznode:// can be used to link to a particular "page" ezobject:// can't.