Thanks James that's a good idea. It would be nice to have an idea of the install base too. I'm thinking what I might do is implement the proxy idea, but also have a facility where people with their own API key can go direct. I need to think about this a bit more though!
Liam On Sat, 2010-05-29 at 16:03 +0100, James Blessing wrote: > On 29/05/2010 14:28, Liam Green-Hughes wrote: > > > Does anyone have any advice about how this should be handled? Has anyone > > else written a client side app for TWFY, if so how do you handle it? I > > don't want to distribute the code (which will be open source) with my > > API key in it so what is the best way to deal with this? > > At first glance I would suggest that you should split the code into 2 > functions, the app part that assembles most of the query and then the > the part that needs the API key sat on a remote site that acts as a > proxy combining the requst with the key and returning the result to the app. > > The added bonus is that the central site can then track requests and > generate information about the app usage. > > J > _______________________________________________ Mailing list [email protected] Archive, settings, or unsubscribe: https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
