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 9 years ago.
Improve this question
I don't know if this question is too simplistic - but are there any sort of best practices or guidelines when it comes to deciding how much data is too much for client side processing (sorting/filtering) with AngularJS.
I am wondering if it make sense to build some sort of trigger into my code - perhaps when the data set reaches a certain size do all manipulation on the server side, if its below that size do it on client side. Is that overkill? Am I over thinking this?
Thanks for your feedback!
You should only every send the amount of data to the client that it needs, that includes aggregate data if the client only needs aggregate data.
The most to send is also however much the client need to function.
Optimise for performance AFTER you have a working client, not before.
This is true for any client, not just Angular.
Related
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 am building a quiz app with Ionic React. I want to implement some kind of quiz timer/countdown feature to limit time spent on every question. The catch is, if I implement a countdown function on client side or Front-end, I'm afraid that folks could tamper with the script and cheat by manipulating the timer to their advantage.
Therefore, I think the only way to prevent this is to implement the timer/countdown feature server side. However, I do not know the right way to go about this... Wouldn't a countdown function blocks the server? Or is there some other way that I do not know?
There are two ways to handle this:
http:
You can run a timer at frontend. Notify the backend with start / end timestamp of each question to calculate the duration taken for each question. If the duration falls within the allowed range, you are good to proceed. Here, frontend is your source of truth but you are validating it at the backend.
websocket:
Or you can implement a websocket to communicate in real time with the backend. In this case, you can run the timer at backend and show its progress at frontend in realtime. Backend will be your single source of truth.
You can check this post too.
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 6 years ago.
Improve this question
So question is do we need backend framework e.g. Laverel etc. if we user Angular\React? Don't undestend why we need cuz i use baclend only for REST API, I can not understand why they can be useful if we do all job on froendend
The need for server side code is largely independent from the use of client side code.
Many projects require server side and client side code in order to function at all (e.g. if data needs to be shared between users of a site). Even those that don't usually should involve server side code as a best practise.
Given a project where server side code is needed, there is never a need for a framework. A framework is a tool that can (in some circumstances) make the development of code easier, but can always be replaced with from scratch code. A developer should select the most appropriate tool for the job.
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 6 years ago.
Improve this question
So I'm developing a 2d game using sdl1.2 on linux as a part of a college project and I need the player to be able to submit his score to know his ranking against other players who played the game aswell and I was wondering what am I going to need in order to achieve this with C, is socket programming the answer?
Thank you.
Yes, if your concern is about the communication, then socket is the only way, of course there are easy to use wrappers around socket, like zeromq etc.
The server would create a server socket and listens on it, and each client will connect to this server and then send the scores and any other data necessary to the server.
For data persistent, you can use embedded database like SQLite or leveldb etc.
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
Facebook's own product uses GraphQL and is also a great example of a realtime experience. E.g. when someone likes something, everyone can see the like appear in their feed.
But all of the documentation for GraphQL uses a stateless server where every query is like making an HTTP GET or HTTP POST at a single point in time.
So it's not clear how the average developer will be able to build something as realtime as Facebook itself.
E.g. what kind of state will the server track when we have realtime GraphQL? Will the client send over a bundle of GraphQL queries to watch? Or will the server track a higher-level aspect of the client's state to infer which GraphQL queries the client cares about watching?
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I'm using a stream engine that updates my database every second with significant set of data.
I would suggest looking into using a WCF Duplex Service. I found several articles about implementing it searching for "Silverlight WCF Duplex Service." You should also consider bring back chunks of your data instead of the whole set each time if the data set is significantly large as you mentioned.