Nate, I think we've cleared this up in person since your message, but
for the record:
Pods don't manage student data. A SAIL Data Service implementation
handles that. The pods do hold Rim objects with are handles for data
in the SDS.
I think your use case re: metadata is students annotating the stuff
they're working with. In our last face-to-face (at Bongo Burger) we
decided that a separate "student annotation" service would be the
right way to go.
-t
On 12/1/06, Nathaniel Titterton <[EMAIL PROTECTED]> wrote:
Pods are motivated by reuse scenarios, and are the sole means for
persistence content and student data -- I've got that. (Even if it
isn't right, I've got it!).
My question: what should happen to pods during the time that the student
is working (i.e., after unmarshalling but before marshalling)? Are PAS
(and CUPS) objects supposed to be agnostic about pods, to the extent
that the pod instances might be garbage collected away at any point?
That makes sense, but how do the PAS instances deal with student data
that in generated in their context? There must be something written
about this, but I couldn't find it.
This issue will also come up with metadata, assuming there are PAS/CUPS
nodes that want to know about this metadata.
-nate
--
-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-+=+-
Nathaniel Titterton [EMAIL PROTECTED]
Lecturer, Researcher 510-643-4207
U.C. Berkeley (329 Soda Hall)
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SAIL-Dev" 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/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---
