Re: Django and Rich Client

On Jun 9, 9:10 pm, Knack <knack...@googlemail.com> wrote:
> Current plans are:
>
> 1) Using an Oracle DB
> 2) LDAP authentification
> 3) Role based authorisation. Here I'm a bit unsure about the approach.
> I would implement it by myself within the django world (don't know yet
> where exactly).

If your application has any workflow to manage, django-workflows is
great,
but the documentation needs help.

It ties into django-permissions which is great.

> 4) Transfering the data using a web service via https. Here are my
> biggest uncertainties. What kind of web service to use? Rest, xml-rpc
> or soap? How to package the acual data? Embedded in the html or xml?
> As binary payload? I would need only basic stuff like log in, log out,
> read and write whole database rows, which are basically the business
> objects. Most of the logic is done on the rich client. I would
> transfer large amounts (100000s of business objects) of data at
> startup time (very eager loading to the client). But also lazy loading
> of course.

My recommendation is Piston, although I am not sure how it would
handle such large
data sets. If you are not doing a lot of writing, you can simply cache
the objects
outside the webserver.

> 5) One important concept is that I change only a small amount of the
> data objects. Most of the changes lead to new versions. Therefore I
> hope to be able to use caching extensivly. The data objects which are
> immutable could be permanently cached in memory. How about
> authorisation of these cached objects? Are there ways django takes
> care of this?

As far as authorization on cached objects - and by this I assume you
mean
database instances, django only provides a very primitive (IMO)
permissions system.

For anything more complicated than that, you need to look at other
systems.

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