hello, cl-http hackers!
several questions:
1) is anyone using http headers to retain state information? if so, i'd appreciate an example.
2) it appears the cl-http authentication routine is called with every url access, which is when the user object is created. i'm doing my own authentication and would like to create my own user objects. if anyone is doing this, i'd appreciate an example.
3) is there a way to make user objects persistent? if so, (you guessed it) i'd appreciate an example.
4) since most web sites use a login form and retain state information without using http authorization, wouldn't it be a good idea to include code for this purpose within cl-http? it would certainly save us from continuously reinventing the wheel and give us more time to develop apps.
thanks!
conrad
