about summary refs log tree commit diff stats
path: root/092socket.mu
Commit message (Collapse)AuthorAgeFilesLines
* 3705 - switch to tested file-system primitivesKartik K. Agaram2016-12-111-1/+1
|
* 3656Kartik K. Agaram2016-11-101-1/+1
| | | | | | | | | | | | | | Periodic cleanup to replace 'reply' with 'return' everywhere in the repo. I use 'reply' for students to help reinforce the metaphor of function calls as being like messages through a pipe. But that causes 'reply' to get into my muscle memory when writing Mu code for myself, and I worry that that makes Mu seem unnecessarily alien to anybody reading on Github. Perhaps I should just give it up? I'll try using 'return' with my next student.
* 3602Kartik K. Agaram2016-10-271-13/+7
| | | | | Simplify primitive interface to read from a socket: now returns just a single character.
* 3601Kartik K. Agaram2016-10-271-1/+1
| | | | | Now we can just read a single character from the socket, and it isn't much slower either (maybe 10%).
* 3586Kartik K. Agaram2016-10-241-6/+6
| | | | Make sure we clear the socket variable after closing it.
* 3585Kartik K. Agaram2016-10-241-7/+0
|
* 3581Kartik K. Agaram2016-10-241-1/+16
| | | | | | | Fix CI. 3 different memory leaks in the socket internals. The hard one was recognizing the need for `receive-from-client-socket-and-close`.
* 3580Kartik K. Agaram2016-10-241-1/+1
|
* 3574Kartik K. Agaram2016-10-231-11/+11
| | | | Shorter branches above longer ones.
* 3573 - client socket testsKartik K. Agaram2016-10-231-2/+23
| | | | This is just the same as tests for a fake file-system.
* 3572 - new way to write server testsKartik K. Agaram2016-10-231-126/+43
| | | | | | | | | | | | | This time we're opening real sockets so we might run into issues on machines with firewalls. Macs for example flash up a dialog warning people about a port being opened, though it shuts down immediately if the test passes. On the flip side, the test has greater verisimilitude. You don't really need fakes except when you want to pin down the environment a test runs in. The only way this test might be flaky is on a machine that has lots of sockets open (so the random port opened by the test is in use for something else). That and the firewall concern above. Hmm.
* 3571 - make 'read-from-socket' non-blockingKartik K. Agaram2016-10-231-1/+8
| | | | Its interface now mirrors that of 'read-event'.
* 3564Kartik K. Agaram2016-10-231-1/+34
| | | | | Change the interface for reading a URL slightly so that we can directly use the path in `assume-resources`.
* 3562Kartik K. Agaram2016-10-221-125/+105
| | | | Fix CI. Revert accidentally-added files.
* 3561Kartik K. Agaram2016-10-221-105/+125
|
* 3535Kartik K. Agaram2016-10-201-2/+2
|
* 3523 - http client now workingKartik K. Agaram2016-10-201-5/+47
|
* 3519 - reading lots of data from a socketKartik K. Agaram2016-10-181-3/+6
| | | | | | In the process I've also altered the API of $read-from-socket to return a boolean (eof?) rather than the number of bytes read (which is implicit in the length of the returned array).
* 3518Kartik K. Agaram2016-10-181-2/+0
| | | | The bugfix of commit 3517 allows us to drop this redundant condition.
* 3511Kartik K. Agaram2016-10-161-3/+3
|
* 3510Kartik K. Agaram2016-10-161-0/+37
|
* 3507Kartik K. Agaram2016-10-161-4/+4
|
* 3476Kartik K. Agaram2016-10-071-1/+1
|
* 3465Kartik K. Agaram2016-10-071-5/+8
| | | | Fix a few names in comments.
* 3464Kartik K. Agaram2016-10-071-2/+1
|
* 3463Kartik K. Agaram2016-10-071-5/+4
|
* 3458Stephen Malina2016-10-071-0/+116
Testable network interface and write flow.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-18 18:04:05 +0000