Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have a JavaScript/AngularJS app, which connects with a server via websockets.
Is there an easy way for a load test? For example, I would like to see what happens when the app is called 100x at the same time (so there are 100 connections to the webserver).
Is there a simple way to test it? If I need software for this, it should run local, since the app is on my computer.
Thank you very much!
You can try https://github.com/kidk/felt
It uses real browsers to generate load to a website. It is still a young project, but it might be the solution you are looking for.
(This is my personal project)
Fallowing link may helps to you .
https://github.com/observing/thor
The AngularJS crew have developed Protractor for end-to-end testing
https://docs.angularjs.org/guide/e2e-testing
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 months ago.
Improve this question
I want to do some real-time operations in my backend. In the past, I used the pusher for real-time operations. But its cost is huge. So, I am thinking about using the socket IO itself. Before using it, I thought about asking for it in the stackoverflow community. So, what do you guys suggest? Is it suitable for use on a production server?
Socket.io is already used in production by many big companies for products including Trello, Microsoft Office, Yammer, and Zendesk.
As #Tintin said, it's also very popular on GitHub and NPM.
Socket.io on Github has:
56.2k stars
1.6k watching
10k forks
On npm, it shows more than 4.5 million weekly downloads.
So yeah, I would say a pretty solid choice for production, provided, as with any software, you use it wisely.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I recently started some web-design and when I look for tutorials on youtube I often see people, when checking their code, using some kind of virtual server to upload and then see their page. I was wondering what difference would there be to simply lunch the html file I'm working and see it through my browser? Does it really make a difference to use a local server? and if yes which ways would you recommend to achieve that?
Thanks!
If you just have pure html and css then opening the file in the browser is the exact same as opening it in a server. However, the real difference is with javascript. If you try to make an HTTP request using js to your own site, it will work on a server but will not work if you open it as a file. If you want to start a server, python has a SimpleHTTPServer module, and most code editors have some sort of plugin, like VS Live Server for VS Code.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
i'm did starting learn Node.js. Formerly i used PHP and used Wampserver as local server. Now, when i starting learn Nodejs, some questions appear in my mind;
i'm starting use terminal windows first time and i don't know how i use this method on for example a linux based server i lease. Would you instruct me about this?
should i install wampserver for database in my computer? or have another Nodejs solution? Which is more advantageous?
Thanks for your answers.
If you are learning Node it would probably be better to install something more geared to that like a free mysql database. Another good way to do it is sign up for a free Amazon AWS account, you can really get a good grasp on Node by working with Lamda and EC2.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I look for the best way to hide the code of a solution built with Electron.
Any ideas?
To build the solution with Electron having asar files is not enough. I really need to hide the code so it should not be easy to retrieve.
There are some possibilities. Take a look at https://developers.google.com/closure/library/docs/closurebuilder. It produces a Java' compiled output content (.jar). Then, you can use a jar module for Node.JS in order to access the internal content (like https://www.npmjs.com/package/jarfile).
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm creating a php app where almost all requests are in ajax and some Jquery effects, so some of my pages are up to 2000 lines of code, all my jquery in one big $document.ready{}, is it normal? should I be ashamed of showing this code to other developers? or is there a better way of organasing Jquery code ?
Like how many others have said, if it's maintainable and easy to read then it shouldn't be much of an issue. However, in my experiences, code that is organized into separate logical modules were MUCH easier to read and maintain than one long document.
With that being said, the typical workflow these days with tools such as browserify would be to refactor and separate the code such that each file executes a specific task for development purposes and when it is time to deploy to production, one would use a build tool to group/minify and optimize for the browser.