I'll really be thankful if someone can help with this.
Should we allow classes to be used as keys for indexBy ( no matter if
they're not unique ) or should we restrict indexBy to unique keys?
Mauro
Chris Chabot wrote:
Cassie do you have any thoughts about how you will want to do this on
the Java side?
It seems to be that it might be container specific if any given field
is unique or not, and things like unstructured names -could- also
overlap (i'm sure there's could be lot of john doe's in most SNS's :P)
Do we want to allow classes to be used as keys for indexBy or no?
If we do, then toString is a great way to make it work (in php and
java alike)
-- Chris
On Jul 16, 2008, at 5:15 PM, Mauro Gonzalez wrote:
hello,
I'm working on the REST indexBy feature, and I have the following issue,
Among the several fields that could be user for indexing a people
request, some of then can work as a key straightforward, but others,
since they're objects, they need to be converted to a string somehow.
ie yo index by name, I need to do somethink like $key =
$nameObj->getUnstructured(); and I need to check every property to
know wether it's an object or not.
I was thinking about adding a __toString() method to those objects.
Any ideas?
As I see, the content of entry in the RestFulCollection object in
the ResponseItem returned by the PeopleService->getPeople is a
regular array, but it depends on the implementation of the service.
Shouldn't it be an array of Person Objects?
Mauro
