New answers tagged

2

Two things to understand about CORS: CORS is not for authenticating/approving the client, it is for approving a request originating from code executing within a web page on one origin that is destined to another origin (like JavaScript code on domain1.com making an XmlHttpRequest to domain2.com). CORS enforcement is entirely client-side. The server does ...


0

Using AJAX is not just for interactivity. Displaying new data and updating a section of the page is a valid approach. Thus, this is IMHO a legal use case. There is an aspect of the described behavior which impacts usability. That is the user sees an empty page and then out of a sudden data appears. This is solvable using loaders or pre-rendering and ...


2

Do we really need a Value Object and Data Transfer Objects for every use case? Why not send back entities? OK, I'm only going to try to answer this one of your many questions. Option 1: If your database exactly models your business, and there are no arcane business rules, then by all means use entity objects in your GUI layer. The programming will be ...


0

The typical way to do this is to have a branch for each feature to merged in to master when done. For production releases, make a release branch off master. For e.g. nightly builds, just run the latest master. You shouldn't need any long-running branches except master and published release branches.


0

Rather than doing the calculations by hand it might be beneficial (depending on the complexity of the queries of course) to use an OLAP server. Some OLAP servers support creating MOLAP or HOLAP cubes that have pre-calculated aggregates that will improve your query performance significantly (E.g http://kylin.apache.org/).


0

PostgreSQL would be slightly better, because its design leans more towards analytical workload, unlike MySQL which was designed for transactional workload. That is if you want to do the calculations directly in the database. Getting player statistics is analysis of the data. The obvious drawback (while not really that important) of PostgreSQL is its lesser ...


0

If I understand well your design, the general idea of the interaction between the parts of your system would look somewhat like this: So you are using tags for 2 purposes: let the server know if the request is to be parsed (no tag) or if the request was parsed and provides parameters to be extracted (tag indicating a command/transaction to perform) ...


-2

wouldn't it take longer to stream the file vs sending whole file at a time? Welcome to the time space tradeoff. Reading a whole file into memory (say as an array or string) is called slurping. It can be a good or bad idea depending on file size, available memory, and how many times you do it at the same time. The alternative is line by line processing (...


2

WCF uses SOAP, which has a lot of overhead to use. In this case, you would probably need to auto generate clients for particular platforms, because it would be too much work by hand. There are a lot of features in WCF, but it has generally fallen out of favor due to the communication overhead and code required compared to simpler models like ordinary HTTP ...


1

Although its a 3 years old thread, still I'm replying it thinking that it might be helpful to somebody. Table Structure Table_Offer -------- ID FK Name start time end time MandatoryGroup -------- ProductId (FK to product) MixGroup1 -------- ProductId (FK to product) MixGroup2 -------- ProductId (FK to product) Table_offerDetails --------------...


0

I think you should use directives for the DOM elements and controllers for interaction between these directives. DOM manipulation should only be done inside a directive. Fetching a text file could be done inside the controller, but it would be better if you did that through a service. Services can be used for reusable business logic/fetching data. You ...



Top 50 recent answers are included