New answers tagged

0

I suggest looking at event data aggregators like Segment which can send data to both your backend and several analytics services at the same time. This would provide a solve for both your purposes without duplication of event logging in your code.


1

I usually hit three major concerns when building analytics systems. How lossy can the analytics event set be? For example ad blockers tend to block most third party in-browser analytics. Depending on your audience that can be more than 20% of your site visitors. On the other hand more reliable events can impose real performance costs on your systems. How ...


4

Do not think about logging as "I want to log this data" think of it as "I have an event that may be interesting to somebody." The fact that 99% of the time the interested party is an object that takes logging events and then writes to a disk-based log is irrelevant to that mindset. Logging is essentially a producer-consumer event framework What you should ...


0

In general, the overhead involved with AJAX requests is higher. If an Ajax request has, say, 1K of transport overhead, then sending 50 bytes over a single request means that your transfer of actual data is only about 5% efficient. Ajax requests are typically made to RESTful resources. Socket communication is a persistent connection, and seems more suited ...


1

A drag/drop UI typically encourages users to play around with the interface. You may not want to have every UI operation send data back to the server every time they interact with the interface. Depending on the specific interface it may not be an issue, but it's something to think about. What happens to the UI if the server response time starts to grow? How ...


0

One popular current 'state of the art' is to use a RESTful API service on the backend, and the front-end is responsible for data display and sending requests/commands to the server. This is usually done through simple HTTP requests to URLs with special meaning, but many other variants work generally the same way (with some varying details - think SOAP, etc). ...


2

If you value consistency then the service that stores the data should be the definitive 'master' source of what the data looks like. This means that the front end must defer to whatever the service says. Now that doesn't mean it cannot cache results, but it should not make assumptions about logic that may (or may not) be processed on the service. eg. Lets ...


1

Roles are generally used to group users together. For example, we have several moderators on Programmers. Rather than creating a role for each user, we likely have one "moderator" role assigned to multiple users. This makes it easy to see who belongs to what group and to modify permissions for multiple users at once. It sounds like you have a classic case ...


0

I would say that this depends on what your app does, and what are its strong suites. Lets say for the sake of simplicity that your app does one of the 3 things: Combines standard/non-ground-breaking code chunks/practices into a cool new way of organizing or viewing data for users (like, "Twitter for pets!") Reveals some awesome new technology that you have ...


1

I have the same problem, and i realize that. When we create adapter and set it to listview, listview will point to object somewhere in memory which adapter hold, data in this object will show in listview. adapter = new CustomAdapter(data); listview.setadapter(adapter); if we create an object for adapter with another data again and ...


1

If the dataset was expected to stay small, it would probably be faster to filter client-side. But because of this: Initially the data set will be low. But with time it will grow quite big and I want it to be scalable to it can be used for a long time and not break or slow down as data increases. I would recommend server-side filtering. Otherwise, ...



Top 50 recent answers are included