Opps, I meant tab.meta usecase. It's not dublin core metadata (didn't
see any dc elements that fit the need). The expires value is stored in
the lenya:expires element.
--Doug
Doug Chestnut wrote:
Ok, now that those issues have been addressed.
How should we make the experation of a document editable? via the
tab.overview usecase?
--Doug
Andreas Hartmann wrote:
Doug Chestnut wrote:
Andreas Hartmann wrote:
[...]
IMO the Document.getExpires() and ResourceType().getExpires() shouldn't
return a formatted string, but rather either an integer (number of
seconds) or a Date object. The date format is specific to the
particular
usage scenario (HTTP headers), which might be seen as closely
related to
the input module functionality - so IMO the date formatting could be
done by the input module.
WDY (and the others) T?
I agree, I prefer the Date object over the number of seconds,
OK, I think this is the better solution (no javadocs needed to
understand the method)
thanks for the review!
Thanks for the quick response! :)
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
