1. Hello World App
1.1. Extension based framework
1.1.1. has annotations also, but extension is required
1.2. Starts a 'Server'
1.2.1. can do WAR deployment
1.2.1.1. loses functionality
1.2.1.1.1. unsure what functionality
1.3. @Get for binding
1.4. @Get("json") for content negotiation
2. Stutter App
2.1. YATC (Yet Another Twitter Clone)
2.2. Interface defines @Get, @Post etc
2.2.1. I like that idea
2.3. Call Start Server
2.3.1. @override createInboundRoot() {
2.3.1.1. Routers that define URI's and classes to service URI's
2.3.1.2. router.attach(BASE + "/user/{username}", UserServiceResource.class)
2.4. UserServerResource extends ServerResource
2.4.1. static method getAttribute("username")
2.4.2. use New Reference(getReference()) to get the URL to this resource
2.4.2.1. This works because its extending a class and you register classes to urls
2.4.2.2. but useful in an abstract sense of 'Reference' if its not just a String
2.5. Automatic Jackson mapping, pseudo XML mapping
2.5.1. May be better w/ JAXB or others
2.6. Rest Client
2.6.1. Using pojos to call interfaces
2.6.2. ClientResource.create(BASE + "/users", UserListManager.class)
2.6.2.1. Rest interface to call .addUser()
3. Overview of REST
3.1. Wikipedia is a great resource
4. Richardson Maturity Model
4.1. `Different levels of rest to reach the - Glory of REST
5. Overview of Reslet
5.1. Summary is a lot like Spring
5.2. An implementation, not a spec (to contrast jee)
5.3. Jackon/JSON auto binding
5.4. XML/JAXB binding
5.4.1. Unclear if its automagic like jackson
5.5. GWT Support
5.6. Cloud deployment
5.6.1. android
5.6.2. google app engine
5.6.3. etc
5.7. 'Client' support
5.7.1. Java calling other REST resources