API is just "Application Programming Interface", i.e. an interface.
It doesn't have to be a networked API (Web APIs); it can also be a
On Thu, Oct 4, 2012 at 11:03 PM, Mike Schinkel <mikeschin...@gmail.com> wrote:--
> Isn't this essentially the "code-on-demand" aspect of REST?
> On Oct 4, 2012, at 9:47 PM, Kin Lane <kinl...@gmail.com> wrote:
> I don't think you are whack. It's more of the conundrum that is the last
> If you build a button, badget, widget or sophisticated JS app. It's client
> Google Maps was built for hackability. I remember Lars talking about this
> Companies like Band Page, do the JS embed driven by API, but don't release
> I think naming matters. I think your right. JS API is not right, but I
> I find advocating for an API is first. Whether you make that public or not
> I think JS is inherently client side or SDK...but then again NodeJS has
> But great conversation and thoughts. I think you have opened up something,
> And needs more discussion.
> Kin Lane
> ** Attending API Strategy & Practice conference? **
> On Thu, Oct 4, 2012 at 4:36 PM, landlessness <br...@apigee.com> wrote:
>> This is a silly question, but it's on my mind.
>> Along the way whenever I visited their dev sites
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.