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)
you see, that's why I can't be left alone with a programming language, I don't know shit.
Since we all live as RocketMan - numbies will be my sig
That service would be provided by your web browser... :)
Well, tried to just enter something in the top box and got sent away but now I am back about to make a non historical supporting post. There's spell check in here too?
How cool is that?
This, apparently, being the first thing that gets asked.
Well, it's not much, but it's here:
What happens if someone puts in a URL? The framework should translate the special characters, but it is the blog software itself that should translate it into a clickable link.
Of course, that doesn't mean I can't make a function to turn URLs into links automatically (and do other post-entry formatting of blog post text) and include it in Rockets...
Today's function turned out to be well suited for a macro. (create-record) takes a couple of arguments. The first is a string which holds the name of the table you are updating. The rest is kind of cool. You put in a bunch of variable names--any number is fine--and what you do is make the variable name the same as the FIELD name in your table. Then the macro takes the names and values of these variables and constructs a valid SQL statement (after filtering each value for SQL injection issues)
So, for example, to add a post in this blog, I just have to write:
(create-record "Posts" Id PosterId PostDate PostSubject PostContent)
and it generates a valid SQLite query to insert the values into the field names that are the variables Id, PosterId, etc.
The magic comes from newLISPs (sym) function, which converts a string into a valid symbol, and the (args) feature of newLISP macros, which allow a dynamic number of arguments to be passed to the macro.
Here's the code that converts the variable names into symbols:
(dolist (s (rest (args)))
(set 'temp-index-num (string 'idx)) ; we need to number the symbols to keep them in the correct order
(if (= (length temp-index-num) 1) (set 'temp-index-num (string "0" temp-index-num))) ; leading 0 keeps the max at 100.
(sym (string temp-index-num s) 'DB))
Wow, this is kind of historic! This is the very first post on the newLISP on Rockets blog. Right now Rockets is barely functional (version 0.04!) but it's just enough to host itself and handle input to forms and connect to a SQLite 3 database.
It's nothing earth-shattering so far, but I want to start "eating my own dogfood" as it were, so this blog will be running on Rockets from the very beginning. As I add features, I'll post about them in the blog.