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 am implementing a web application which uses React as front end and Asp.net as backend. I have around 2000 images that has to be used in the web application. What will be best way to store these images ?
The best way is never store any media yourself.
Since serving any image/video content relies heavily on your network/bandwidth, it is not always stable and vulnerable to the slightest DDoS attack. Let alone that the security of your server may not be enough to protect your data.
I would highly recommend you to lookup some CDN, or Content Delivery Network, provider, such as AWS and GCD. You may also set up access right and serve criteria to better protect your data in these providers.
Reference:Why Use CDN’s for Your Website & Image Hosting
Edit: I just noticed that you have tagged your question with azure-storage, which is also a great option for serving media over the internet.
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 6 years ago.
Improve this question
Meteor.js integrates well inside a Mantra.js architecture, but does it have advantages since it slows the running of my requests.
For instance a dummy request in GraphQL (get a random string from the server) runs in few ms using Apollo Client and 1 second and more using Mantra.js (exact same request wrapping Apollo stack).
It only depends what kind of project you want to work on.
Mantra.js is an architecture framework for Meteor.js, that means :
it helps a developer to follow the creation and development of its modules corresponding to the Mantra framework. The developer is free to use any kind of front-end library he/she wants, any Data Query and Client caching he wants, but in my opinion, it doesn't really improve the quality of the code. Someone can organize a project with own rules and it can be maintainable easily.
So if your team is comfortable with your code structure you definitively don't need something like Mantra.js.
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 6 years ago.
Improve this question
So I recently stumbled upon jscrambler.com
This tool actually allows you to protect your javascript code, its fascinating. However, the service is cloud based and im wondering if this is really ok. Since im actually posting code on their servers. While others cant steal my code, it is still vurnerable to theft from within the the guys behind jscrambler.
Maybe im worrying too much. Is it safe to use jscrambler services?
You're right. Giving your code to a 3rd party to protect it is as counter-productive as it is counter-intuitive.
That said, browser users always have access to the underlying Javascript code. The most you can do is wrangle the source code by making syntactic changes that produce the same functionality but result in harder-to-read text.
This process is known as uglification or minification (since it reduces file size). UglifyJS is the most frequently used tool for this.
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 making a website for a client that will mostly be used offline through a wifi router. But there will also be an online version available. The purpose of this is to distribute files in parts of the world where infrastructure is not suitable for internet access. For those who do have internet access in some of these parts, the internet probably isn't very fast or reliable.
Some of the pages I've made can be accessed simply by using JS functions to hide one page and show another, instead of anchoring to another file. I figured this method might load content quicker, rather than linking to multiple pages. But is that true? Or should I just put all the content on separate pages?
Yes, that's true, but most browsers doesn't load a page if they don't get an answer, so you'll need at least one local server. You can store almost everything (style, script and content) in localstorage, store as strings and eval if/when needed. Also, if local processing isn't a problem you can use AngularJS to build and rebuild the page.
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 8 years ago.
Improve this question
If we are running two different node instance one of each purpose( webservice engine/data engine and webservice consumer) will it be good or keeping both the purpose in same application will be better ?
Yes it is.
One project is your API, the second project is the access to your API by web.
Maybe in the future you might need a mobile app to connect with the API or maybe the webapp technology becomes obsolete and you might need to replace it for another modern technology, so that you don't have to change your API.
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 2 years ago.
Improve this question
I want to develop a web-based collaborative editing app: basically many users will transcribe a big mp3. The first step is to write a specification.
It seems pretty easy to do it with async communication and javascript, keeping track of the transcription an user gives and forwarding it to other users editing the same file, but I fear I might be underestimating the problem: what are the common issues this kind of problem raises?
Thanks!
You didn't specify what browsers you want to support. To do it "real-time", you can either poll the server or use Comet or WebSocket (for browsers that support it) or Flash net Socket. As with any collaborative app, I think the hardest problem is conflict resolution/keeping all sessions synchronized.
You might be interested in reading Google Wave Protocol too. It's a white paper on real-time collaborative document editing. Not for the faint of heart :D