TFTP Server?

I think dropping the file into some sort of class (along the lines of the http-server-in-an-irule) is a possibility, but the TFTP protocol specifies 512 byte chunks sent to the client after each previous one is ACK'ed.

 

 

1. client sends RRQ (opcode 1) with filename

 

 

2. Server sends block 1, client rx's and ACKs block 1.

 

 

3. Server sends block 2, client acks block 2, and so on.

 

 

4. As soon as the client gets a block thats <512 bytes, it knows that this is the final block.

 

 

We can also do away with the necessity of handling write-requests (WRQ, opcode 2), since this is read-only. Respond to them with opcode 5 ("error", along with an error number and some useful ascii text).