I think that helps, yes. It sounds like my original solution is viable, to store the full XML spec in the DB.
I'd suggest creating a field of type "text" (or whatever the equivalent for your RDMS is). You should then be able to have server- side coding that allows the professor to upload the XML text for the chosen gadgets, and then serves them back out for students when they log in. Hope you find that useful, String On Feb 13, 8:45 pm, Chipou <[email protected]> wrote: > Ok. I think that you help me with your answer but I want to rexplain > my case. > On the website, a professor can propose a list of exercises (coded on > the form of a gadget) to his student. He saves gadgets which want that > student do. Also, when student connect on the website (a session > different as the professor) they can consult exercises that the > professor choose before. But I don't know how save gadgets to students > have access to the exercises. > > I hope I clarify the situation... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" 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-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
