Most of the client plumbing is not specific to the Twitter API. There are some compatible assumptions (e.g., comma-separated parameters), but most of it is just a skin around net/http. Pull this out into a separate package.
The layer graph is now:
http, types
twitter
users, tweets, auth, ostatus
Most of the auth package could be lifted further up the graph, but for now I've left it alone.
Most of the client plumbing is not specific to the Twitter API. There are some compatible assumptions (e.g., comma-separated parameters), but most of it is just a skin around net/http. Pull this out into a separate package.
The layer graph is now:
http,typestwitterusers,tweets,auth,ostatusMost of the auth package could be lifted further up the graph, but for now I've left it alone.