Thanks! I hadn't known about "contentcreationtime" - exactly what I
would like to ensure the creation date/time remains to before my robot
edited a blip on being added to a wave much later.
Is the value in milliseconds like the example on the FAQ? (It's got 3
extra zeros)
I tried the following (with values of "0", "1249309218000",
"1249309218", etc.) and I couldn't get the client to show a date/time
other than the last edit date on the blip:
if (tempEventType==EventType.BLIP_SUBMITTED) {
Blip tempBlip = tempEvent.getBlip();
List<Annotation> tempCreationTimes = tempBlip.getDocument
().getAnnotations("contentcreationtime");
if (tempCreationTimes.isEmpty()) {
tempBlip.getDocument().setAnnotation("contentcreationtime",
"1249309218");
} else {
for (Annotation tempCreationTime : tempCreationTimes) {
LOG.warning("contentcreationtime
"+tempCreationTime.getValue());
}
}
}
Perhaps I'm just misunderstanding things. =) Could you add a note on
if the annotation names are case-sensitive?
On Dec 2, 3:33 am, "pamela (Google Employee)" <[email protected]>
wrote:
> Just posted a new FAQ about supported annotations:
>
> http://wave-api-faq.appspot.com/#annotations
>
> Comments/suggestions welcome.
>
> - pamela
--
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-wave-api?hl=en.
