>>>> 2) If there is significant benefit, how can we model
this using the
>>>> simpler type system?
>>>
>>> Easy - I can add a PROPERTY_EXPRESSION type which attempts to resolve
>>> the expression when you call asString()/asInt()/etc. (toString() would
>>> return the expression).
>>>
>>
>> This would need to be done on the server side and the calculated result
>> shipped to the client.
>
> I'm not sure this is really necessary. I'd think we'd have runtime
> operations available to query the actual values in use for these kinds
> of things; I think for regular model queries the user would want to read
> back the expressions only.
>
This is true. The client can decide how to handle this themselves.
Simply returning PROPERTY_EXPRESSION from ModelNode.getType() is enough
to tell the client that the value needs to be resolved; they can decide
what to do with that information.
How would a client resolve the expression ? Or rather - how could the client get the
effective value of the property as seen by the server ?
/max