Re: [pylons-discuss] Re: middleware vs components for auth

2015-07-20 Thread Jonathan Vanasco
On Saturday, July 18, 2015 at 11:35:44 AM UTC-4, Iain Duncan wrote: > Off topic: have you tried the new glass for your glasses that changes the > colour balance to reduce eye strain? I used to get very frequent migraines > from coding, and an updated prescription with the the new fancy glass

Re: [pylons-discuss] Re: middleware vs components for auth

2015-07-18 Thread Iain Duncan
Thanks Jonathan > Sorry, I've had a migraine and eye-strain all week and can't seem to > phrase questions (or anything) right. > > Off topic: have you tried the new glass for your glasses that changes the colour balance to reduce eye strain? I used to get very frequent migraines from coding, and

Re: [pylons-discuss] Re: middleware vs components for auth

2015-07-17 Thread Jonathan Vanasco
On Friday, July 17, 2015 at 6:53:05 PM UTC-4, Iain Duncan wrote: > > > Cached I think. > ... > I'd say medium. Normally low, but occasionally we could be dealing with > 1 user type traffic. > Sorry, I've had a migraine and eye-strain all week and can't seem to phrase questions (or anything

Re: [pylons-discuss] Re: middleware vs components for auth

2015-07-17 Thread Iain Duncan
Hi Jonathan can you share how you envision the auth policy to work in any detail? > > 1. simple access > Access will be from Angular apps, so will be pretty straightforward ajax requests initiated from javascript. > 2. fine grained ACLs > Yup, we intend to use ACLs for row-level permissions >

[pylons-discuss] Re: middleware vs components for auth

2015-07-17 Thread Jonathan Vanasco
can you share how you envision the auth policy to work in any detail? 1. simple access 2. fine grained ACLs 3. auth can be cached for X amount of time OR auth may need to be immediately revoked/updated 4. will this be high load, low traffic, somewhere in between -- You received this message be

Re: [pylons-discuss] Re: middleware vs components for auth

2015-07-17 Thread Iain Duncan
Right now our thoughts are that we'd like each app to be able to run on it's own EC2 instance if need be, but the databases will all be on one database server. thanks! On Fri, Jul 17, 2015 at 9:32 AM, Iain Duncan wrote: > Thanks Jonathan. The inner apps could well be on different machines in th

Re: [pylons-discuss] Re: middleware vs components for auth

2015-07-17 Thread Iain Duncan
Thanks Jonathan. The inner apps could well be on different machines in the future, we are intending to design around that if possible. This is an area I really don't know much about, so any suggestions or pointers at good resources would be great. Ideally we come up with some scheme where an auth a

[pylons-discuss] Re: middleware vs components for auth

2015-07-17 Thread Jonathan Vanasco
a third option is to use a tween, which would basically be a hybrid of a middleware and a sharedlib. the question I have is on the logistics of deployment -- are these different apps going to be on the same machine or will they be on different machines? also, how will you coordinate updates an