RE: Re: backrefs using ref name / annotations?

 
> references are inherently 2 way, they just happen to be 
> stored on the source.  for most cases, having a special field 
> or class is overkill.
> 
> fyi, there is already an api for backrefs.

Apps have a need to occasionally treat BRefs like regular references,
for use in things like ReferenceField.  Just getBRefs() and
getBRelationships() alone underwhelm.  Ideally, one would have:

1. a table of configurable relationship name inverse mappings:
	"requires" -> "required by"
	"uses" -> "used by"
	
2. a proxy to the reference catalog (remap relationship names and
ref->bref equivalents) to make using #1 as easy as using regular
references - without actually mucking with ReferenceEngine internals.
To get this working with ReferenceField and Referenceable, would likely
need monkey patch.

Justification, from some yet unrealized thoughts from a few years ago:
http://mail.zope.org/pipermail/zodb-dev/2003-May/005019.html
http://sourceforge.net/mailarchive/message.php?msg_id=5165984

Sean


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642