david rasch - making stuff work » rest http://www.davidrasch.com Mon, 04 Apr 2011 00:53:25 +0000 en hourly 1 http://wordpress.org/?v=3.1.2 API Access to Users’ Data http://www.davidrasch.com/2006/10/01/api-access-to-users-data/ http://www.davidrasch.com/2006/10/01/api-access-to-users-data/#comments Mon, 02 Oct 2006 03:06:18 +0000 drasch http://www.davidrasch.com/2006/10/01/api-access-to-users-data/ Apparently our API discussion at PHP Appalachia struck quite a chord with Michael.

As we’re in the process of building up the IntelliContact API, we’ve run into this same problem. We’ve taken a bit of a simple solution. We allow a given user to associate an API key with their account and specify . . . → Read More: API Access to Users’ Data]]> Apparently our API discussion at PHP Appalachia struck quite a chord with Michael.

As we’re in the process of building up the IntelliContact API, we’ve run into this same problem. We’ve taken a bit of a simple solution. We allow a given user to associate an API key with their account and specify a separate password. This allows the application using the API to access only users accounts to which they’ve been granted, and leaves the power with the user to revoke the access at will by changing the password or disabling the API key access entirely. This seems to be a simple-end solution to what Michael proposes which allows for a more general ACL.

[tags]API, REST, authentication[/tags]

]]> http://www.davidrasch.com/2006/10/01/api-access-to-users-data/feed/ 1 launching a beta http://www.davidrasch.com/2006/06/26/launching-a-beta/ http://www.davidrasch.com/2006/06/26/launching-a-beta/#comments Tue, 27 Jun 2006 03:10:43 +0000 david http://www.davidrasch.com/2006/06/26/launching-a-beta/ A beta usually sounds like a great idea, but with the difficulties of software development–hitting deadlines, feature drift, and push to release biding time can be challenging. Both agile development and patience paid off in this case. In the preparations for our 4.0 beta, we spent an entire sprint (28 days) dealing with our . . . → Read More: launching a beta]]> A beta usually sounds like a great idea, but with the difficulties of software development–hitting deadlines, feature drift, and push to release biding time can be challenging. Both agile development and patience paid off in this case. In the preparations for our 4.0 beta, we spent an entire sprint (28 days) dealing with our internal feedback of things that were ‘non-optional’ to fix before our ultimate release. Now, we’re “waiting” a sprint for feedback to roll in.

The challenge comes in distilling the feedback and determining the value of what has been said and suggested, and what hasn’t been said. For example, if everyone talks about the size of the new icons (which are intentionally quite large) does it mean that they thought most everything else was great? Or does it mean they stopped looking after they were scared away by the large icons?

The triage process as will begin next week where we decide what of the feedback gets rolled into the software now, what goes into the product backlog for later, and what gets ‘held’ for further input, suggestion, or interest.

Meanwhile, the development teams have been hard at work playing with buzzwords like RSS and REST.

[tags]intellicontact, beta, rss, rest, scrum[/tags]

]]> http://www.davidrasch.com/2006/06/26/launching-a-beta/feed/ 0