soaplib <https://github.com/soaplib/>

On Thu, Jun 9, 2011 at 1:10 PM, Knack <knack...@googlemail.com> wrote:

> Hi guys,
>
> I've got a prototype DB + Rich Client app and need to make a proper
> production app out of it. The client is written in PyQt and needs to
> fullfill quite some functional and performance requirements (I would
> really like to keep it). The client connects directly to the DB.
>
> After some thoughts about security I came to the conclusion that using
> django is the way to go. Now I seek some coarse advice / feedback
> wether I'm heading in the right directions. I've got some miles to go
> and looking forward to learning Django, but want to avoid newbie
> pitfalls. So if something of the following sounds like bad ideas to
> you, please let me know ;-).
>
> 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).
> 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
>

I recommend you REsT, IMHO XML-RPC is not fast, SOAP is a good option but we
get just few libraries under development soaplib[1]  is really promise.


or soap? How to package the acual data? Embedded in the html or xml?
>

Just be light.


Regards,

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.
> 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?
>
> A long first post ;-). Any comments are appreciated!
>
> Cheers,
>
> Jan
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>


-- 
Cristian Salamea
@ovnicraft

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to