thoughts about a web fw

jamp.md

(1) = exists in preview state (2) = planned next (3) = planned

main stuff

• completely free and open source
• convention over configuration
• simple to use
• reliable
• small

use common protocols and standards

• id + json (1)
• http (1)
• owin (1)
• get, post, put, patch, delete (1)
• /resource (1)
• cors (1)
• oauth (3)
• basicauth (2)
• [usertoken] (2)

have persistence providers built in

• only send id + json back and forth (1)

• caching built in (1)

• persist first by default (2)

• filebased (for config settings et c) (1)

• esent based (for concurrent data) (1)

• sql based (if sql is a requirement) (1)

• url based (another web fw data endpoint) (1)

streaming / websockets

• websockets sync built in as a complement to rest (1)

future: content serv

• owin staticfiles (3)
• razor (3)