Greg Reimer

That's a good question and I'm open to suggestions. Two ideas off the top of my head: 1. `ng-if="ngf('some_list', i, 'some_prop').indexOf(searchText)"` 2. Create a custom filter that accepts `i` and...

Thanks for finding this. It might be a couple of issues. Upgrading the code to use http.request() (which reuses client objects) speeds things up considerably. But it still reports failed...

And for me at least it was throwing "too many listeners" errors, since it was adding listeners to the same socket each time when connection was reused in keepalive mode....

Which version of node are you on? The fix for the performance issues has dependencies on the client connection pooling in 0.4.x.

Thanks. Incidentally I'm also doing my tests on an Apache "It works!" page. The failed requests are some weird low-level stream issue that I'm still trying to understand. Will reply...

Version check added.

I realize this is old, but can anyone comment if this is still an issue? v0.x branch is still around if fixes are badly needed.

There should be a test case for this. I'm adding a todo as a reminder.

I've been hearing about this from others too, but haven't been able to isolate it myself. I wrapped the offending line in a try/catch and pushed the change to github,...

Does hoxy print any errors? Can you add ``` proxy.log('error warn'); ``` ...to your script and paste here any errors it generates? That should just print all errors to stderr.