Well,
It begins from this: https://nodejs.org/api/http.html
Thanks for your help,
On Wednesday, May 2, 2012 at 11:05:58 AM UTC+7, ss9 wrote:
I have a unique app I need to build:
1. Gets a request from a browser
2. Passes a call to a TCP server which sends a UUID to a 3rd party
3.
there's an answer I can find in the internet.
On Wed, May 13, 2015 at 10:59 AM, Tom Boutell t...@punkave.com wrote:
Node is third party software (:
On Tuesday, May 12, 2015 at 8:53:24 AM UTC-4, Ket wrote:
Can you point out how built it from scratch. Using third party software
cause a lot
Can you point out how built it from scratch. Using third party software
cause a lot of headache.
On Thursday, May 3, 2012 at 10:53:56 AM UTC+7, Evan wrote:
Applications like this are why I built http://actionherojs.com/
Let me know what you think!
On Tuesday, May 1, 2012 9:05:58 PM UTC-7,
Hi guys,
I've this simple server code structure. It broadcasts message from a client
to all connected clients. However, all connections have been cut off when
someone refresh the page. Anyone can point out what wrong with my code?
var WebSocketServer = require('ws').Server;
var wsServer = new
Base on my google research, something like this is working fine on Linux
environment:
http://stackoverflow.com/questions/16724216/node-js-0-10-7-cluster-support-for-udp-dgram
But I work mostly on Windows 7 and 8 before upload things to the Linux
server.
Is there any hack available to get it
I've tried this
https://github.com/ebidel/html5can/tree/master/demos/audio_streamer
It works.
But there's a lot to be done to get the stream smooth.
On Thursday, April 10, 2014 12:01:10 PM UTC+7, Nathan Rajlich wrote:
I've done experimenting with this in the past, and in fact I've written a
I use to send and receive data on the server using this method:
On the client:
var a = { b: 'data1', c: 'data2' },
d = JSON.stringify({ type:'string', data: a });
socket.send(d);
On the server:
ws.on('message', function(message) {
var json = JSON.parse(message),
b =
If this is real time data streaming, it is pretty fast. Impressive. Never
see something working smoothly like this before.
How much data in bytes do you send each time.
On Tuesday, March 25, 2014 11:28:26 PM UTC+7, Postlethwaite wrote:
We at Plotly have just released our Streaming API (our
Thank you so much. It's time to start learning and build something awesome
:)
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs
Hi guys,
I'm wondering is there anyway or if it possible at all to send data
directly from node.js server to Arduino or Espruino board (via mobile phone
service, Wi-Fi, etc.).
If yes or possible, how to do it?
Thank you,
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
I used that before. It seems it does nothing.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send
this as possible.
Ket
On Sunday, February 23, 2014 11:48:34 AM UTC+7, Unmesh Joshi wrote:
Hi Nitin,
The buzz around handling millions of connections by single node server,
should be interpreted as, 'it can handle lot more connections, provided it
has enough CPU and memory, as compared
It would not work great unless you now how to slice float32array into
chunks and reassembled them in the other end. Sending data frame have very
high lag time.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You
Thanks for the info.
Your explanation is crystal clear. But because I do not understand this
processes so I cannot describe my problem clearly.
I communicate with my app through WebSocket. When using port 8080 I can
access to it from my home and work computer but Android mobile devices.
When
Hi again,
I haven't answer your quest in a previous reply.
It's part of my web application. With out the app, it's just plain blank
page.
Thanks
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received
Thanks,
What about port 554? My app streaming data real time (ArrayBuffer + JSON)
in a large scale.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the
I use node.js to communicate with my web applications real time.
When I assign port 80, it is conflicted with Apache port 80 and I cannot
access to the app from my mobile devices.
But when I assign port 37, I cannot access to it from my work computer.
So which port is safe for commercial use
http://websocketstest.com/
It seems it's the only one on the web that demonstrates send and receive
data on Chrome Beta for Android. I desperately need to use this feature.
I'm using einaros's ws and it doesn't work.
Thank you,
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Thank you,
Do you mean they send data from browser to browser?
How do they do that?
I've never heard of something like that.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you
@ Alan Hoffmeister, Thanks. I used to use WebRTC. I agree it's much faster
but that doesn't suit my needs. So I stick to node.js and WebSocket.
And thank you guys for suggestions.
It seems that Chrome Beta for Android receive data sent from a server but
it doesn't send data to a server. I hope
Yes, thank you to bring it back.
I think I've asked in the wrong forum and I deleted it.
I feel very downbeat only to see the work I've been doing days and nights
doesn't work when it comes alive. I've targeted android devices (Chrome
Beta for Android specific) since the first place. I feel
I've tested my web application on several android mobile devices
(smartphone, tablets). None of it works.
The test link is here: http://meldville.com/demo/broadcaster.php
It streams audio and video data to here:
http://meldville.com/demo/audience.php
It just only works on Chrome Beta for
Thanks, after some research. I picked the 64 bit package.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this
Sorry for a dumb question. I'm not an IT guy so I don't know the different
of the two.
I've a 2GB RAM server on a2hosting.com and planned to upgrade in a near
future.
Which package is better suit for me.
PS. I run a 32bit package previously. But I've reinstalled Ubuntu and have
to restart the
Thanks,
I got it.
--
Meldville http://www.meldville.com
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this
On one end of the websocket pipeline I’ve an application that let user
stream data in a json format.
On the other end, I pick up data frame of five senders at random. Each data
frame will contain the sender identity and message.
For each data frame I picked up, I separate the sender
To put it simple. I'm trying to do what node.js does on the server on the
browser, especially on Chrome.
In node.js, node recognizes who send the data and processes or passes it
through accordingly like something below:
var connections = [];
wsServer.on('connection', function(ws) {
I encoded UTF-16 character and it works fine. It depends on the code and
file type that you encode the characters.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are
For flash check. The code above won't work. I solve this problem long ago.
Can't remember how I did it.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the
I have the same idea. I think node.js is an ideal for office and home
automation, if not beyond.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Hello,
I try to send data with the child_process function in a use strict mode
with the code below:
normal.send(socket, broadcast(i, message));
var broadcast = function(i, message) {
this.i = i;
this.message = message;
var sendData = function(i, message) {
this.i = i;
Thanks, it appears to work.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to
I'm streaming media data (audio, video) through node.js server to connected
clients.
However, I found that it is not yet suitable for commercial purpose at this
stage due to huge streaming latency and server costs, let alone bandwidth
usage.
On my specific searching that focuses on TCP and
Thank you,
I've no clue about these. I think I should have a serious study now.
starting with multicast perhaps...
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are
I'm actually interested in this. Is it happened with every other case?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To
Thank you,
You've saved me my hair. I use proxy server, if this the case, in part of a
plan to expand service to other region.
There's nothing happening because there's no data transfer. It's the
problem I tried to solve for weeks and Google didn't help me a bit.
--
--
Job Board:
I got this error message:
WebSocket connection to 'ws://75.98.171.173:8080/' failed: Error during
WebSocket handshake: Sec-WebSocket-Protocol mismatch
Can any one please tell me what went wrong? I double checked everything and
still can't figure out what is the cause of the problem. I've used
According to Google engineer team (the audio team), WebRTC is the way to
go. For now, node.js is not yet powerful enough to stream audio live due to
huge latency. You have to reduce sound quality in exchange for speed. Flash
is still better. In the future, we have yet to see.
And besides, RTC
It keeps your app running even error or worker dies. I think node.js app
naturally dies if error occurred.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to
Thanks for response, it's still not working.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send
This cause the app stop.
Here's my code. I run it as root:
start on filesystem or runlevel [2345]
stop on shutdown
script
export HOME=/root
exec /usr/local/bin/node /usr/local/bin/myapp.js /var/log/myapp.log
21
end script
Thanks
--
--
Job Board: http://jobs.nodejs.org/
OK. I give up.
What is the alternative to Upstart that does not cause this problem.
Thank you.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Hi,
I do not understand why this block of codes is not working on Ubuntu 12.04
(server) but it's working fine on Windows 7 (home computer):
var WebSocketServer = require('websocket').server;
var http = require('http');
var fs = require('fs');
var server = http.createServer(function(request,
Actually, it works if I run the app manually. But it doesn't work if I use
Upstart to run it. Thank you.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the
I've upgraded my Ubuntu OS from a dev version to a stable one. The code
below work fine with the unstable version:
description node.js server
author kvz
start on startup
stop on shutdown
script
export HOME=/root
exec /usr/local/bin/node /where/yourprogram.js
Thanks for response,
Does this node.js library has something to do with the problem:
https://github.com/nodejitsu/node-http-proxy
I take it from this tutorial:
http://cjihrig.com/blog/scaling-node-js-applications/
It works fine on my home computer (one computer only) but not on the server.
I use the cluster module according this manual:
http://nodejs.org/api/cluster.html
The block of code is:
var cluster = require('cluster');var http = require('http');var numCPUs =
require('os').cpus().length
if (cluster.isMaster) {
// Fork workers.
for (var i = 0; i numCPUs; i++) {
Thank you,
I've downgrade the websocket module and it fixed.
On Mon, Jul 22, 2013 at 8:44 PM, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Mon, Jul 22, 2013 at 1:04 PM, Ket kettin...@gmail.com wrote:
I use the cluster module according this manual:
http://nodejs.org/api/cluster.html
I want to do memory object pooling for my node.js application.
How do I track memory performance of an app that run on a server?
In chrome, I just open a dev tool and view memory graph in real time.
Thank you,
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Can you elaborate about that a bit more please. I don't know how to dump
memory heap with V8-profiler.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the
Thank you
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To
Thank you,
I always think server side is faster because it is run by C++. But user
base would grow over time. Use sense sometimes not make sense.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this
I've an identical processing javascript function that run on both node.js
server and a browser (chrome). I've no idea how to test which side is
faster.
Does it's the right idea to run it on a server and render on chrome, or
should I process on chrome alone.
In this case, does node.js act as
On the side note: This is server sent application.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group,
You are confusing me!
On Friday, July 12, 2013 11:20:48 PM UTC+7, Kaveh Shahbazian wrote:
I forgot to say that yet in most cases Node.JS performs better than Go -
of course in a little threshold.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
I've tired the code below it isn't worked:
var WebSocketServer = require('ws').Server;
var wsServer = new WebSocketServer({port: 8080});
wsServer.on('connection', function(ws) {
if (ws.origin != 'http://example.com') {
console.log('Origin was not http://example.com');
Thanks, the code I use is exactly same as the example. It works on node.js
version 0.6.15 on windows but it's not working with version 0.11.3.
And thanks for sharing about socket.remoteAddress.
On Wednesday, July 10, 2013 4:30:13 AM UTC+7, ryandesign wrote:
On Jul 8, 2013, at 21:00, Ket
Hi,
I begin to study RTC Data channel from this example:
link: http://www.simpl.info/rtcdatachannel/
It is great except that I can't send data to anywhere. Even I declare
server like:
var servers = {
servers: [{
url: 'stun:stun.l.google.com:19302'
}]
};
Anyone has any
The library I use is: https://github.com/joyent/node
I thought I installed version 0.6.17.
But when I check as suggests on this thread:
http://stackoverflow.com/questions/5356113/how-to-check-which-version-of-v8-is-installed-with-my-nodejs
It said v0.11.3-pre. (Sorry, I just want to check it
headline:
link:
http://nodejs.org/api/child_process.html#child_process_example_sending_socket_object
How do you get socket.remoteAddress? All I can get is a null string.
Thanks,
Ket
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List
You could do that with standard audio API and websocket. But javascript
application behavior, including node.js, is unpredictable on different
machines, OS and browsers.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
the message parsing in.
Of-course I intend to use Edge.js
(http://tjanczuk.github.io/edge/http://tjanczuk.github.io/edge/#/)
to do the heavy lifting. I wish Node had a good FFI and I would like to see
a project like Edge.js for Go.
@Ket These are the results:
A TCP Echo Server
1
I looked into your code. It's just ordinary server code. I always struggle
with node data transfer in sending multiple large binary objects
simultaneously. It is good to see any comparison.
On Saturday, June 22, 2013 11:03:42 PM UTC+7, Matteo Collina wrote:
Hi Kaveh,
the MQTT.js
Great to know!
This is the first time I ever heard of such performance comparison
experiment. Keep going...
On Tuesday, June 25, 2013 12:01:24 PM UTC+7, Kaveh Shahbazian wrote:
@Ket I have tested the code with a 8 KB message too (instead of ping
string). Performance drops but still Node
That's excellent,
Any chance you're willing to share the idea of increase node.js server
transferring speed? My application is depending heavily on node speed.
On Friday, June 14, 2013 12:35:12 AM UTC+7, Scott Miller wrote:
So just to update, I'm able to push my transfer rate to ~850Mbps. I
This is very interesting. I always have problem with node.js speed as I use
node to stream audio and video data in real time. No one have ever test
real-time data transfer speed and my file reading is almost instance
because preload data into the buffer.
For file reading speed using fs method.
I use gzip and child_process api and I see performance increase
dramatically.
However, I feel that performance could be improve further.
Is there any other method do you suggest.
Thank you,
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
I just finished building an app (basically). It's like Voxer but you can
keep talking and listening to the other people until you close it.
The buffer size per each data frame transfer is about 73xxx bytes, x2 for
bidirectional communication.
The test is working well between two computers, and
This is intrigued.
The initial calculation is inaccurate. Buffer requires some space for
breathing. So data frame is much larger.
Can you please tell me more about *cluster coremodule*.
Where should I start.
Thank you so much.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
OK. I find this thread :
http://stackoverflow.com/questions/11620648/whats-the-difference-between-node-js-cluster-module-and-learnboosts-cluster-m
That's too bad. I'm using v 0.6.18 on the web server.
Thanks
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Thanks for sharing. That's excellent!
On Wednesday, February 20, 2013 4:12:58 AM UTC+7, Vitaly Puzrin wrote:
Finally :)
http://nginx.com/news/nginx-websockets.html
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
There is no memory leak at all if you write javascript effectively. Write
the code that release memory when not in use. Node.js free memory (or
garbage collector i'm not sure) pretty fast. No memory leak detect software
needed. Save your saver space and memory.
On Monday, February 18, 2013
I done it on the client side before piping through.
On Sunday, February 17, 2013 2:07:00 AM UTC+7, aaronheckmann wrote:
Thanks all!
On Saturday, February 16, 2013, Nathan Rajlich wrote:
objectMode is for the *implementor* of the Writable stream. I.e. if I'm
writing a writable stream
Hi,
I'm just wondering why I cannot send a binary data larger than 64k bytes.
And by 64k bytes I mean 64 x 1024 = 65,536 bytes.
Thank you
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message
. Please give us more information
How and where do you send them?
What are the modules you use?
On Wed, Jan 23, 2013 at 4:49 PM, mscdex msc...@gmail.com javascript:wrote:
On Jan 23, 4:05 am, Ket kettin...@gmail.com wrote:
Hi,
I'm just wondering why I cannot send a binary data larger than
It's Worlize here: https://github.com/Worlize/WebSocket-Node
I have no idea if different sever-side vendors make different performance.
On Wednesday, January 23, 2013 11:38:58 PM UTC+7, mscdex wrote:
On Jan 23, 10:14 am, Ket kettin...@gmail.com wrote:
It's just the codes I've taken from
Do you mean the stream can be split into frames. How?
I heard about buffer. Do you think I can send data in pieces of buffer?
On Thursday, January 24, 2013 8:00:50 AM UTC+7, Bradley Meck wrote:
Are we talking about the frame limitation here? Packets above a certain
size will be split into
I have the same issue.
How do you clear outgoingFrameQueue?
Thanks
On Thursday, November 29, 2012 6:20:32 AM UTC+7, Phil wrote:
I found the issue!
The outgoingFrameQueue doesn't clear itself. So, the array just increases
indefinitely. I clear it after my send, and no memory leak!
On
, Ket kett...@gmail.com javascript:wrote:
I have the same issue.
How do you clear outgoingFrameQueue?
Thanks
On Thursday, November 29, 2012 6:20:32 AM UTC+7, Phil wrote:
I found the issue!
The outgoingFrameQueue doesn't clear itself. So, the array just
increases indefinitely. I clear
Can you please tell me more about the Stream module. I've never heard about
it.
Thanks
On Saturday, January 12, 2013 1:18:47 PM UTC+7, hacksparrow wrote:
The large file in JSON format could be the likely cause. The Stream module
might be what you want to use.
El Capitan
--
Job Board:
://gist.github.com/4073604).
It will generate heapdumps that you can analyze later on chrome.
Luis
--
On Fri, Jan 11, 2013 at 2:17 AM, Ket kettin...@gmail.com wrote:
Hi,
I've an experience that my app eat up my web server memory and it stop
working.
How do you release memory when the app
Hi,
I've an experience that my app eat up my web server memory and it stop
working.
How do you release memory when the app is not in use and how do you manage
memory allotment so that node.js would not use up all the memory again and
again.
Thank you.
--
Job Board: http://jobs.nodejs.org/
-collect unused memory.
You'll want to survey your app for objects that grow without bounds and
figure out if/how/why they should be growing like that.
On Thursday, January 10, 2013 6:17:21 PM UTC-8, Ket wrote:
Hi,
I've an experience that my app eat up my web server memory and it stop
on what your're doing,
it could be much slower. Are you proxying data through a pure js websocket
implementation? If so, that will eat a ton of cpu decoding the websocket
protocol thanks to the framing mask.
On Jan 8, 2013 2:35 AM, Ket kett...@gmail.com javascript: wrote:
Thank you
well with nodejs as the server component would be a win.
That said, I don't know enough about the WebRTC stuff at this point. I
know people have done good work bringing the streams api to the browser for
things like this.
Unfortunately, I'm not sure any of this is going to help Ket
side uses
webrtc technology.
You can see it at work at http://www.meldville.com/
Is there any ways I can increase my streaming speed over the internet?
Thank you in advance and sorry for my poor English.
Ket
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent
Thank for reply,
That's correct. Anyone here insist that node is super fast. You are the
first to mention that.
I don't know about nginx and will look into it. Is it faster than node.js.
Thanks
On Tuesday, January 8, 2013 12:53:48 PM UTC+7, Mark Hahn wrote:
The server-side is processed by
Are there any other ways you recommend can make the stream as fast as on my
computer, a local network, or at least comparable to flash.
I heard some people send data in chunks. Is this possible to make it faster?
Thank you,
On Tue, Jan 8, 2013 at 1:37 PM, Mark Hahn m...@hahnca.com wrote:
For
PM UTC+8, Ket wrote:
It's not easy to achieve what you want with javascript alone. I would use
PHP for this project.
On Tuesday, December 18, 2012 1:36:44 PM UTC+7, ayaz ali wrote:
hello everyone
i have developed chat appusing express and socket.io which is currently
chat rooms based i
It's not easy to achieve what you want with javascript alone. I would use
PHP for this project.
On Tuesday, December 18, 2012 1:36:44 PM UTC+7, ayaz ali wrote:
hello everyone
i have developed chat appusing express and socket.io which is currently
chat rooms based i want to extend it now for
are different on Linux.
I can't make my app live online with Windows, so I switch to Linux.
Sorry for absurdly stupid.
I have to lean Linux a bit, I guess.
Thank you.
Ket
On Sunday, December 9, 2012 2:58:03 PM UTC+7, Juan Simon wrote:
Let's see if I can help.
I'm not experienced enough with node
Hello,
I found that the speed of file sending through node.js in a jason format
has been reduced dramatically.
Anyone know how to speed this thing up. My file sending speed is virtually
real time without json. But with it, file receiving is almost 4 minute
delay in the other end.
Thank you,
people who live on a fixed
income too.
Thanks,
On Sunday, December 9, 2012 11:53:18 AM UTC+7, Mark Hahn wrote:
That makes no sense. A file is a file. The contents of the file
should not affect the speed it is sent.
On Sat, Dec 8, 2012 at 8:43 PM, Ket kett...@gmail.com javascript:
wrote
. But it is fast enough with the other goodies if
provides.
Node does not take much resources and it run on any common hardware.
Please tell us what you trying to do. any sample code, then we can help
you out.
On Sun, Dec 9, 2012 at 10:50 AM, Ket kett...@gmail.com javascript:wrote:
nodejs
Hi,
I feel that I don't like Forever much to keep my app restarted when it
stopped.
Is there any other methods around to replace Forever.
Thanks
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this
Hello,
I've encountered a strange experience. When I tried to stream media, I mean
huge media, through the network using node.js, the client side receives an
uneven stream so it's not quite smooth viewing.
Base on my research (Googling), some people say that node.js consumes a lot
of memory.
:00 AM UTC+7, Eric S wrote:
On Monday, November 19, 2012 7:52:43 PM UTC-8, Ket wrote:
Base on my research (Googling), some people say that node.js consumes a
lot of memory. Is this true?
It can be. In my limited experience, that has a LOT more to do with how
you code your application
Hi,
I've developed my app under the Windows environment. But when it comes to a
real world usage I have to host my app under a Linux plan. Does this cause
me to change my code accordingly. If it does, it will be a makeover I guess.
Just my concern!
Thanks
--
Job Board:
Don't boast them much just yet they have taken down some cool MP4 video
features. What do they think better video format than mp4 you guess.
Yes, I can use ogg but that is the case.
On Friday, September 7, 2012 1:13:14 AM UTC+7, Dennis Kane wrote:
Hi! I've got a really slick Desktop GUI
Sound complicated, but thanks to give me a clue.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send
1 - 100 of 118 matches
Mail list logo
