MIME-Version: 1.0
Received: by 10.151.47.7 with SMTP id z7mr15486ybj.8.1236878753734; Thu, 12 
	Mar 2009 10:25:53 -0700 (PDT)
Date: Thu, 12 Mar 2009 10:25:53 -0700 (PDT)
In-Reply-To: <429425890903111531q5d927229sb73f09db1c7c0eac@mail.gmail.com>
X-IP: 78.52.201.189
References: <c5d3a1ae-82a9-4dad-8c53-aa2bbb4ec785@a12g2000yqm.googlegroups.com> 
	<429425890903111531q5d927229sb73f09db1c7c0eac@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) 
	Gecko/2009020911 Ubuntu/8.04 (hardy) Firefox/3.0.6,gzip(gfe),gzip(gfe)
Message-ID: <de4e54be-3729-4678-b61f-31992da0303f@h5g2000yqh.googlegroups.com>
Subject: Re: request for clarification
From: esc <emergencyselfconstr...@googlemail.com>
To: digitaltunesapi <digitaltunesapi@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi again,

What would you suggest for users to use as "application name" when
registering for an api-key?

esc

On Mar 11, 11:31=A0pm, William Coates <william.coa...@gmail.com> wrote:
> Hi,
>
> I guess the best idea is to make the key configurable in your code, so
> people can use their own key: don't distribute it with your key. You
> could make it read from a config file or environment variable or such
> thing...
>
> 2009/3/11 esc <emergencyselfconstr...@googlemail.com>:
>
>
>
> > Hi,
>
> > i hacked together a tiny tool to use your api that allows me to track
> > artist and label releases. I was wondering what to do about the api-
> > key if i give the tool to my mates, or make it available online. Does
> > each user need his/her own api-key? Or should i distribute the api-key
> > with the tool? The tool is written in python and i was a bit worried
> > that if i put the api-key online in clear text, someone might go and
> > do mischief with it.
>
> > thanks
>