Building a new app in python and need some architecture advice.

[Sam Watson]

>What do you mean exactly with "across the web"? Over HTTP? Port 80?
>"in a secure fashion": SSL? Encrypted? Authentication? Authorization?
>So many options ;-)
>
I dont know exactly what i mean :)  It doesnt matter to me as long as
its secure.  I dont really need stateless because this thing aint
gonna scale past 10 users and keeping state solves a bunch o problems.

>Yes. Pyro has support for secure custom connection
>validators that can be used to authorize clients to connect
>(by using an authentication mechanism of your own choice,
>for instance login+password based, or with secure hashes,...).
>You can also run Pyro over SSL if you want encryption.
>(although I must say that it's been a long time since I
>did this, so it might or might not work. If I have some
>spare time, I'll check the SSL stuff, but I'm too busy
>with other things at the moment).
>
It sounds like pyro may do the trick here.   The thing it would seem I
would be losing with pyro is the ease of iterating and linking maps
and lists of objects.  Can I do this transparently with pyro?  

I'll investigate further.  Thanks for the help!


>> Twisted  (Is this overkill?)
>Don't know, depends on your type of server application I guess.
>
its nothing special.  your basic data entry app with some minor
reporting.  Simple as it gets.

>> Pure sockets (a lot of infrastructure to write but im pretty
>> experienced with it)
>
>Why write it when you don't have to (see other options).
>
The only reason I would write it myself would be control, performance,
and ultimate flexibility.  It doesnt seem very pythonish tho.