20 reputation
3
bio website
location
age
visits member for 2 years, 5 months
seen Apr 6 at 4:44

Jul
29
comment Designing a persistent asynchronous TCP protocol
See also WebSocket.
Jul
13
awarded  Editor
Jul
13
accepted Designing a persistent asynchronous TCP protocol
Jul
13
revised Designing a persistent asynchronous TCP protocol
Explanation of solution, and choice of answer.
Jun
24
comment Designing a persistent asynchronous TCP protocol
HTTP(s) is a little bloated for this sort of thing, which is not really a big deal. The problem is you'd either have to make clients make regular GETs which is sloppy or make the server "push" as-needed on a keep-alive which seems even worse. How might this be implemented without making a disgusting hack of your web server?
Jun
24
asked Designing a persistent asynchronous TCP protocol
Jun
23
accepted let users group do “sudo -u username chown”
Mar
28
awarded  Student
Mar
26
comment let users group do “sudo -u username chown”
By the way I'd vote you up but my reputation precedes me.
Mar
26
comment let users group do “sudo -u username chown”
You are right. I am attempting to make this work with chmod instead of chown. I have some files owned by "dummy" that should be inaccessible to anyone (including dummy, basically, since hes got no shell and no password and his account is expired). However if a user (group "users") needs to access such a file, they can run a script that lets somebody know and then makes a lockfile and does sudo -u dummy and changes file ownership -- make that permissions ...May be easier just to put these files in "users" group and setup a script that watches file access times or something.
Mar
26
awarded  Scholar
Mar
26
asked let users group do “sudo -u username chown”