a tad
> since it is sync rather than async) but you don't loose any messages
>
> console.log is synchronous as well, has been since 0.6, iirc.
>
>
>
> On Thu, Mar 21, 2013 at 2:58 PM, Nathanael Anderson
> wrote:
> >
> >
> > On Thursday, March 21, 2013 4:2
We recently encountered an issue with our node.js application (based in
express.js and socket.io). After a while the application won't respond to
any I/O or if only erratically. It still accepts tcp connections (or http
connections) but doesn't respond at all. Furthermore it can't establish
network
on which platform are you developing the app? I have seen the null value
when the imagemagick binary segfaulted... this happened to me on macos and
some linux distributions.
On Tue, Feb 12, 2013 at 8:10 AM, Mark Hahn wrote:
> I use the identify command to get the image metadata.
>
>
> On Tue, F
If you don't want to script too much on you own you can use this
interesting little porject:
https://github.com/newsapps/beeswithmachineguns
For my stress tests I wrote a small node application which emulated the
behaviour of our clients (using superagent and socket.io-client) and remote
controll
AM, Jonathan Dahan wrote:
>
>> From the same article, try
>>
>> c++filt < stacks.out > demangled.out
>>
>>
>> On Wednesday, January 30, 2013 4:44:35 PM UTC-5, Lars Jacob wrote:
>>>
>>> Hi,
>>>
>>> I try to generate one of
Hi,
I try to generate one of this nice flame graphs of my node application,
following the blog entry here:
http://dtrace.org/blogs/dap/2012/04/25/profiling-node-js/
I got already so far to install an openindiana virtual machine, compiled
node (v0.8.18, 32bit environment, --with-dtrace) and got so
Hi Ayaz,
Probably it's falling back to xhr-polling because you have some firewall or
proxy somewhere between your client and your server. Socket.io
unfortunately first tries websockets and than falls back to other methods
by default which takes some time. The fallback timeout can be configured
(se
