Mark Evenson comments

Results 181 comments of


                                            Mark Evenson

RocketLauncherUI Integration OR Added Feature Support

Fairly complicated reasoning about what should occur in , for which there doesn't appear to be a clear consensus.

Can't Install on Lion - Safari 5.1.1

For installing Safari Ominibar 1.5 for Safari 5.1.2, I was able to get it to install via: ``` osx$ sudo open Safari\ Omnibar-1.5.pkg ```

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

The thread errors were due to my slightly unorthodox use of the clients collection on the `websocket-resource`. In order to implement various networks of publish/subscribe clients, I was calling the...

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

The write lock problem exposes a "slight weakness" in `hunchensocket` that pull request #25 prevents. Without explictly moving the state of the client away from `:disconnected`, code that has obtained...

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

>websocket timeout is really two independent timeouts to Not possible to set separate read and write timeouts on the websocket The problem is really that the two timeouts are independent:...

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

No, there isn't only one timeout: there are separate timers. If either one goes off, the socket is destroyed. It *seems* like there is one timeout to the `hunchensocket` user....

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

As a user of `hunchensocket` I simply want one timeout. But `hunchentoot` apes the behavior of `setsockopt()` which has two independent timers. So, it is rather impossible for `hunchensocket` to...

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

One can't instruct `hunchentoot` to re-arm the timeouts. That is implementation dependent, if possible at all. There is only a `set-timeouts.lisp`.

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

`set-timeouts.lisp` is the file compilation unit in `hunchentoot` involving its timeout API.

The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.

Sure, one could set a client side timer to push request/response messages across the wire, but that requires that the client explicitly code such logic which isn't as "clean" as...