
//  Created by Jason Terhorst on 2/10/10.
//  Copyright 2010 Jason Terhorst. All rights reserved.
//

// Well, Hello there!

 ## JTBookmarkEngine currently handles two services: Delicious and Instapaper. 

-- Advantages:
 1. Abstracting the different APIs into something Cocoa-like, consistent, and simple. You don't have to worry about keeping track of the changes.
 2. The APIs are sometimes finicky and strict. The engine knows when to delay/process requests to avoid angering the service.
 3. Don't worry about networking stuff. We do that for you. Works on iPhone OS 3.0+ or Snow Leopard.

-- Classes:
 Main: JTBookmarkEngine - the hub class, stores/serves up the user's input.
 this main class calls these classes:
 -> JTDeliciousController - calls the Delicious API. It handles the HTTP auth stuff, but requires two strings: username and password.
	Returns: posts (array), tags (dictionary of groups/keys, with arrays of strings)
	actions:
		- posts
		- addPost:withDescription:withNotes:andTags:
		- deletePost:
		- tags
		- deleteTag:
		- renameTag:toNewName:
	#IMPORTANT: all of these return a BOOL value. You'll need to spawn this off to a thread if you want async action. It just blocks its current thread until it's done.
 
 
 -> JTInstapaperController - calls the Instapaper API. Currently, you can only add new items. There's no way yet to see items or add items to folders on Instapaper.
	Returns: (currently, no lists or anything can be retreived)
	actions:
		- addPost:withTitle:
	#IMPORTANT: all of these return a BOOL value. You'll need to spawn this off to a thread if you want async action. It just blocks its current thread until it's done.
 