On Sun, Apr 22, 2007 at 04:43:27AM -0700, Joe wrote:
> It sounds like you shouldn't be using Django, honestly. You would be
> fighting against/hacking around most of the functionality of django
> because django is an MVC framework and you guys basically are trying
> to re-write the model
It sounds like you shouldn't be using Django, honestly. You would be
fighting against/hacking around most of the functionality of django
because django is an MVC framework and you guys basically are trying
to re-write the model architecture. If you really really really want
to use django, you
Hi Brandon,
On Fri, Apr 20, 2007 at 01:58:48PM -0400, [EMAIL PROTECTED] wrote:
> I want to try out Django for a small project, hoping to discover that
> it will be the web framework of my dreams, but I need some advice.
>
> My project group has written an xml-rpc API in front of our database
>
Hey, seeing as you haven't had any relies yet, I will through my idea down.
What I think you're gonna have to do for the most graceful version is to
create your own database wrapper, that calls xml-rpc, instead of an
actual database. Then Django *should* be free to use. The problem may
occur
I want to try out Django for a small project, hoping to discover that
it will be the web framework of my dreams, but I need some advice.
My project group has written an xml-rpc API in front of our database
and password stores. This means that when we want to, say, create a
campus guest account,
5 matches
Mail list logo
