Re: zogi - birthDate attribute of Contact

Hi Adam,

I don't specifically need to use the birthDate attribute, but who knows 
what clients might ask for ;-)  Basically, I'm trying to exercise OGO and 
the different xml-rpc bindings to find out where things might go 
pear-shaped. 
 
I assume from what you are saying that the zOGI xml struct for other 
entities (e.g. tasks) will also be inconsistent when it comes to empty 
date values (i.e. that they will be outputted as string types, but expect 
dateTime.iso8601 types? 

I'm not sure what to suggest.  As Helge intimates, using 1001-01-01 is a 
hack, but then probably any solution to this is going to be a hack.  What 
does OGO's original xml-rpc binding do with empty date values? 

Bernard





Re: [OGo-XML-RPC] zogi - birthDate attribute of Contact

Adam Tauno Williams 
to:
xmlrpc
08/06/2008 15:19


Sent by:
[email protected]
Please respond to xmlrpc







This is a tough issue as each environment treats dates differently,
most XML-RPC bindings don't provide a NULL type, etc.... In .NET a date
value can't be null (stupid!) so it is common to use the MinValue of
DateTime to represent an undefined date.   I've looked around and not
found a nice and clean solution to this issue.   I may just have to
adopt the same solution - making 1001-01-01 indicate no-value-defined.
Would that be acceptable for what you need?  But this requires an
if/else construct in the client protocol handler - which is something in
zOGI I've been trying to avoid as much as possible (protocol wrappers
should be thin).



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