Basically we do a bit more than that. J but we'll pretend. Yeah a Library market would be cool.
Brandon Wirtz BlackWaterOps: President / Lead Mercenary Description: http://www.linkedin.com/img/signature/bg_slate_385x42.jpg Work: 510-992-6548 Toll Free: 866-400-4536 IM: [email protected] (Google Talk) Skype: drakegreene YouTube: <http://www.youtube.com/blackwateropsdotcom> BlackWaterOpsDotCom <http://www.blackwaterops.com/> BlackWater Ops <http://www.cloudonastring.com/> Cloud On A String Mastermind Group From: [email protected] [mailto:[email protected]] On Behalf Of Robert Kluin Sent: Monday, January 30, 2012 10:10 PM To: [email protected] Subject: Re: [google-appengine] Protecting the Source Code of Python When distributing to others You're basically running a memcache proxy, right? Are you wanting to be able to tie into the app itself and cache the rendered output from various sections or something? It would be kind of neat to have a "App Engine Library" market place. To clarify, are you wanting to be able to enable it from an app's dashboard, or saying you'd like to do something like: includes: $PYTHON_MARKET/vendor/package/name/ Maybe if they get "addressable" versions of an app setup you can run your service in more of a standard mode. Even with that, I'd say legal agreements are probably about your best bet. Robert On Mon, Jan 30, 2012 at 19:37, Brandon Wirtz <[email protected]> wrote: > > My CDN In A Box product has always really been a stop gap for clients that we were helping add scale to their applications. > > We have always operated as an App in front of an App, but we are thinking that since what we do a lot of times for companies is help them add the same functionality in to their software that we should make it a python library. Or an import or some variation on this, but we haven't come up with a good way to keep the code safe if we distribute it this way. > > > > I keep hoping that there will be an AppEngine Market place, but there isn't really, and I'm not sure that would do what we want. > > > > Essentially we'd be a nice shim that went in your app, you'd have the handler you wanted to accelerate call our handler, and the name of the handler you would have used. If we had the URL in our cache and it hadn't expired we'd serve it. If we didn't we'd call your handler and cache the result. Instantly your app gains huge amounts of performance and you don't have to work out the optimal caching mechanism for full requests. > > > > Anyone have thoughts on the best way to distribute such code without having it pirated all over the place? > > > > > > Brandon Wirtz > BlackWaterOps: President / Lead Mercenary > > Work: 510-992-6548 > Toll Free: 866-400-4536 > > IM: [email protected] (Google Talk) > Skype: drakegreene > YouTube: BlackWaterOpsDotCom > > BlackWater Ops > > Cloud On A String Mastermind Group > > > > > > -- > You received this message because you are subscribed to the Google Groups "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected] <mailto:google-appengine%[email protected]> . > For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
<<image003.jpg>>
