izaya/1991
1
0
Fork 0
mirror of https://github.com/urlysses/1991.git synced 2024-11-26 11:38:05 +11:00
Code Issues Releases Wiki Activity
31311ee91c
1991/1991.fs

51 lines
1.1 KiB
Forth
Raw Normal View History

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.
2017-02-12 14:16:49 +11:00
\ 1991
1991
2017-02-02 14:26:33 +11:00
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.
2017-02-12 14:16:49 +11:00
include unix/socket.fs
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.
2017-02-14 14:32:00 +11:00
\ User-defined routing
wordlist constant routes
: find-route ( addr u -- data )
routes search-wordlist if
>body @
else 0 then ;
: register-route ( data addr u -- )
2dup routes search-wordlist if
routes drop nip nip
>body !
else
routes get-current >r set-current \ switch definition word lists
nextname create ,
r> set-current
then ;
\ Internal request handling
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.
2017-02-12 14:16:49 +11:00
: read-request ( socket -- addr u ) pad 4096 read-socket ;
: send-response ( addr u socket -- )
dup >R write-socket R> close-socket ;
: start-server { server client }
begin
server 255 listen
server accept-socket to client
client read-request type s\" HTTP/1.1 200 OK\n Content-Type: text/html\n\n fffff" client send-response
again ;
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.
2017-02-14 14:32:00 +11:00
\ Userland
: 1991: ( port -- )
create-server 0 start-server ;
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.
2017-02-12 14:16:49 +11:00
: 1991/ ( "<path> <word>" -- )
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.
2017-02-14 14:32:00 +11:00
bl word ' swap count register-route ;
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.
2017-02-12 14:16:49 +11:00
\ App demo:
: handle-hi ." hi!" ; \ not sure printing is the way to go?
1991/ hi handle-hi
\ 8080 1991:
Reference in New Issue Copy Permalink