Hey all,

Long-ago webhead here who hasn't touched much of anything since
Javascript was a dirty word and PHP was the be-all and end-all (but
I've managed a bit of Python experience) I just have a few questions
about whether or not Django was right for a project I'm thinking of
and hopefully getting a few insights from people who know much more
than me.

Basically, the website is going to centre around user-generated
content. The plan right now is for the users to be able to create and
edit an .XML file (or a series of them?) and eventually 'publish' them
for public consumption. They're essentially slideshows, the XML
describing a combination of pictures and words in a particular
'screen', with each chapter in a publication having a number of
screens, etcetera. It's my understanding that the editting and
creation of the XML files is fairly straightforward and best done with
Javascript, using only Django / Python to save the XML (and depending
on how brave I am, possibly also using AJAX to parse the XML in
'published' mode so that the presentation is done in real time without
having to reload the page for every new screen) I know this is a
Django channel, but does that all sound right?

But what would be the best way to store this XML? Each user could have
a number of XML files. Is it better to have the database describe the
relation between these files and their relative position, or to store
the XML in the database itself? I'm a bit loathe to fill up a database
with blobs, but is this the norm these days? Is there a particular
database that's suited for this?

Thanks for your replies.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to