Should intids be replaced with uuids for relations?

Hi,

during the last years there have been some controversy whether to use 
plone.app.relationfield for relations or just save UUIDs into fields and 
catalog them into portal_catalog.

Since plone.app.contenttypes will use relationfields, that seems to be 
coming the official way.

My only concern is that currently relations rely on intids, and we are 
not using them for anythin else (by default).

Yet, it's not zc.relation (the relation catalog) which requires intids, 
but only z3c.relationfield se depend on. So, I'd guess, it should be 
possible to use uuids instead of intids by dropping z3c.relationfield 
(and all intid-packages) and implementing all required counterparts for 
zc.relation and z3c.form directly in plone.app.relationfield.

Would you see issues with this? Is there some other relation roadmap, 
which I'm missing?

Regards,
Asko


------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk