Closed shizidushu closed 5 years ago
1) fiery handles requests in blocks, collecting them in a queue and then processing them (usually the queue will never get longer than one). The processing of a queue is a cycle
2) there is plenty of literature on websockets and how they work scattered across the internet. I’m not going to list specifics as I don’t know what is best right now
3) setting block = FALSE
launches the server in a way where you can still interact with the terminal (it doesn’t block it)
I just read the fiery reference manual from CRAN. I have several questions (maybe silly).
Cycle
The "minimal example" shutdown automatically after several seconds. It seems the following code does it.
What is the block "Count the number of cycles (internal loops)" does? i.e., what does internal loops mean? How the
cycles
becomes greater than 50? What's cycle incycle-start
andcycle-end
?Message
In the Life Cycle Events, there are
before-message
,message
,after-message
. I don't know what is websocket message. Is there any explanation about it? Or I should read some document/book (any suggestion?)Block
What does the
block
argument inapp$ignite(block = TRUE)
do? How this argument affect the server? i.e., Does it mean a new process/session start when two or more users request the same resource in the same time?