urlysses
b1f03d4e41
There's still a bit more TODO
7年前
urlysses
d775fd9ae6
Add basic CRUD support.
TODO:
+ Make content-type available.
+ Make sure multipart/form-data works (not sure?).
+ Clean up recent code additions.
7年前
urlysses
424aced3ec
Fix 404 typo.
7年前
urlysses
d0558d9621
So focused on keeping track of the stack, didn't realize over over == 2dup.
7年前
urlysses
dfb84bb22d
nip is the optimized version of 'swap drop'. Nice.
7年前
urlysses
7ff8c9942e
Finalize url mapping/url pattern matching.
All that was missing in 574c33c27e
was a
way to retreive the values of our fuzzy matches.
7年前
urlysses
574c33c27e
Add url pattern matching (url mapping?)
TODO: Make the collected vars available to the handler words.
7年前
urlysses
4d08c23f27
Add views + very basic templating support.
7年前
urlysses
f0cac5c8f2
Fix bug where repeat invocations of sourcedir returned different results (due to abuse of sourcefilename memore address)
7年前
urlysses
6310938b54
Add sourcedir for more reliable file paths
7年前
urlysses
1571064535
Add multi-file example
7年前
urlysses
a32c43b989
Basic query string handling.
7年前
urlysses
888cf5ba77
Put todo list somewhere easily accessed
7年前
urlysses
299eef6ecc
Add filetype syntax (register and find).
7年前
urlysses
11a53a7d14
Generalize header words and start implementing content-types based on extensions
7年前
urlysses
a9c21097b8
Move app demo to an examples dir
7年前
urlysses
2eef80dd5d
Implement basic file serving from public/
TODO:
+ set appropriate MIME types
7年前
urlysses
3a8b715b7b
Ignore .DS_Store
7年前
urlysses
b2926d10c2
Handle 404s more appropriately if a requested route fails
7年前
urlysses
a4e3aa169e
Add very basic GET support (route either resolves or doesn't)
TODO:
+ file-serving if no user-defined routes match. Search "public/" dir
unless otherwise specified by user.
+ query arguments
+ PUT, POST, DELETE
+ templating
+ fuzzy-/pattern-match-enabled user routes (e.g., /something/*/wildcard)?
7年前
urlysses
31311ee91c
Save user routing in a wordlist.
The aim is to try to avoid polluting the global wordlist with routing
functions.
The alternative would be to have users simply define words that match
their routes, e.g.:
```
: 1991/hi
( some definition of hi's handler )
;
```
I'm still not entirely convinced that the above method isn't a better
solution.
7年前
urlysses
f40f2d5630
Gotta start somewhere:
First, define a user-facing word that takes a port and subsequently
starts the server (using gforth's unix/socket.fs).
Second, start defining a user-facing word for specifing routes and their
handlers.
7年前
urlysses
1f528fa8f6
1991
7年前