Hi, >Serializing objects to strings just for the purpose of parsing >them again makes little sense to me. ... >doesn't need to be the only way to do it.
+1 >about "flat or not". Forcing getNodes to return things as a hierarchy, >when it also could be a list of objects, decorated with a path, will >make it harder than it needs to be to process efficiently. So far I didn't think this is a problem, but I'm not sure if I understand what you mean exactly. Could you give a example how an alternative representation would look like? >in order to remote things efficiently, we still need to >be able to optimize the number of requests. This means asking for a set >of NodeStates, for a hierarchy, and also filtering the result set (or >selecting specific parts of the hierarchy). +1 Regards, Thomas
