Re: zogi - birthDate attribute of Contact

[email protected] wrote on 09/06/2008 15:10:01:


> If you mean "order" as in attribute A before attribute B then I
> definitely think that is circumstantial and *not* a feature (like
> selecting records from an RDBMS and getting them in the same order every
> time - might happen, but you shouldn't count on it). 

I suspected as much.  So I will end up writing my own binding mechanism, 
or bundling Lua and using its binding. That's ok - it's pretty much what I 
expected.

> You should be able to send any struct you receive from zOGI straight
> back to zOGI unmodified.  That is a design principle,  if there is a
> case where that doesn't work it is a bug. 

Right.  And as far as you know, of the First Class Entity attributes it is 
only when birthDate and completionDate have null values where this is not 
true?

> > Unless dates are output and input as strings.
> 
> Dates as strings would break the binding for rich type languages
> (Java, .NET, etc..) and introduce a need to parse dates on the client.
> That fattens the client side "wrapper",  which is against the zOGI
> design philosophy.
 
Yes, I thought that would be the case

> What I'm thinking is to leave the empty string as the default behavior
> since there are currently client code that deals with it. 

I think you should just leave it as it is.  Once I look at the Lua xml-rpc 
bindings, this may all turn out to be a non-issue.  Sorry if I wasted your 
time, but it was informative for me anyway.

Thanks

Bernard



-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc