On Thu, 15 Nov 2001, brian moseley wrote:
> On Thu, 15 Nov 2001, Stephen Adkins wrote:
>
> > Use the following modules for dates and times
> >
> > Class::Date
> > Date::Parse
> > Date::Format
>
> i propose that we make this our official recommendation for
> p5ee software and that we accept proposals for altering the
> recommendation as they occur.
>
<advocate type="devils">
I'm not actually sure this is something that should be set in stone here
right now. I'm totally with Greg in his point that this project should be
focussed on the middle tier space, but I would also like to suggest that
this implies that we can make no assumptions about the implementation
platform of the adjoining tiers in the application. There may be
compelling reasons for me to implement my UI layer in Java and my data
storage layer in C++ or Ada, I'm going to be looking at interoperability
as a key feature in the platform I use to implement the stuff between
them. So for instance could any of this stuff pick the bits out of :
<prop:sentAt>2000-05-14T03:00:00+08:00</prop:sentAt>
No extra points for guessing what generated that BTW :)
So I think what I am saying is that we do have to define or accept a
standard date format (or formats) for incoming and outgoing data but I
don't think that we should should worry too much about the internal
representation of those dates.
</advocate>
