After much soul-searching, I went ahead and implemented the delayed-write method I talked about in my earlier posts.
At first I tried to overload (print) and (println) and it worked but jumping in and out of different contexts made messed up my ($POST) functions, and I thought I'd simplify my life by just defining new functions: (display) and (displayln). Then at the end you (display-page). You can also (display-image) and (display-post-box). Kind of a theme going there.
Anyway, (set-cookie) now adds a cookie to the header that will get posted when the page itself is displayed. It seems to be working, so hopefully I can now work on getting user sign-in happening on the Rockets blog!
Yes. It was.
Thanks to Bootstrap's "reactive" ability, you'll notice it gets automatically reformatted and the menus work differently.
I think it's pretty neat.
Bootstrap is based on jQuery, which I use a lot and which will be fully integrated into Rockets.
Small and fast....
It's in there. Scroll down to the bottom of the page.
I've been thinking about the Cookie Conundrum and I think it goes beyond just Cookies...
If I want to do a redirect on a page, as Dragonfly does with Response:redirect (something I use all the time) I have to set the headers to be a 302 Redirect. Again, these headers have to be sent before any other text is shown, so it has to be printed at the beginning.
I have changed the way Rockets works to use the Dragonfly model of just loading everything into a big global variable called STDOUT, then delaying printing until the end where you print the headers first and then STDOUT. Only I can't force the delay because there isn't a main program in charge of loading each page, so you have to remember to add the new function (display-page) at the end of your pages for it to work.
Hmm. Not sure about this. I'll think about it some more.
In order to get separate users to sign on and post messages, I need to set some cookies. This leads me to what I call a Cookie Conundrum.
I can define a function to set cookies that is executed somewhere in the page (like rockets-main.lsp) But cookies are set in the header, using the line Set-Cookie. The header is the first thing printed out by the script, and I won't know what the cookie is until later in the script.
What Dragonfly does is caches everything being (print)ed and (println)ed into a big old global variable called STDOUT. Then at the very end of the script it prints the headers (which have already been calculated by the script) followed by STOUT. This involves overriding (changing the default behavior) of (print) and (println). I could do that, but is there a way to do it differently? Can you set a cookie and somehow have it remember to print that cookie in the next header on the following page?
It's something to think about...
Said Han Solo.
No, I'm totally going to add that stuff. Very cool.
There's no millisecond thingy to say how fast this or how many resources were used in its making.Comments (1)