Tag Info

New answers tagged

2

This is a terrible idea if there are no clear warnings on the example page. It encourages developers to put their secrets in their configuration files on their developer machines. Those files end up in version control, which is very, very wrong. The only location where configuration files might have secrets (see below about what I mean by secrets) is on ...


1

I suppose that since my users will navigate between pages, the websocket handshake will have to be remade after each request, which might be bad because of the additional overhead (not so sure though..). Bad in what sense? Yes, there will be additional load on your server, but it probably won't be a big deal. Your main goal at this stage should be to ...


0

Sending data over the wire to an API Is, I think, one of the key drivers of an ADM/POCO style approach to programming (see my question : OOP vs ADM Comparisom where i touch on some of the same points) If you take the OOP route, you are faced with the problems of serializing a model which jealously guards its data and then creating a similar model on the ...


0

I have done both of these approaches in the past and I tend towards the simplified POJOs. The main reason is, it allows and forces in that the business logic is actually performed on the server. When we used to send the full rich model to the client our client code started accumulating little bits and pieces of business logic everywhere and got rather ...


-2

Well this is a nice question and I think most of the developers who work in web application development don't use multithreading explicitly. The reason is quite obvious since you are using a application server to deploy your application, the application server internally manages a thread pool for incoming requests. Then why use multithrading explicitly? ...


1

Semantic web is an approach that has made serious steps during the history of World Wide Web. The field of Artificial Intelligence has also progressed so that it has provided Semantic Web with tools capable to link the semantic information and create Agents that will be able to automate a lot of human everyday activities (e.g. shopping-appointments). ...


0

An interesting problem! I would suggest that a web site itself is unsuited to listening to these TCP streams. Instead I would add an intermeditate layer or two. 1: abstract legacy systems : Create a service which listens to the streams and converts the info into messages which it then places on a queue. (perhapse msmq, zmq or rabbitmq could be used here) ...


2

Those form fields are part of the presentation layer. You should have a view model, basically a model for that presentation. That viewModel has to have the entire state for that form fields. The state should be: their value, their enabled/disabled, etc... So, when you present those fields in the screen you'll have to load the state from your viewModel. ...


7

emails containing an encrypted personId in the query string of an https link Firstly, encryption isn't really what you want in this scenario - you really want entropy. Your login token should be entirely independent of your personId, instead it should be a random string generated using a cryptographically secure method. Of course you will need to ...


1

An application context object usually allows access to the configuration of the application instance, things like: What is the application's hostname and path? How is dependency injection configured, i.e. what implementation is to be used for a given interface? OS environment variables In a properly designed OO system, the access will be via methods of ...


6

You've outlined the pros of doing the app client side only. Here are some possible cons - if any or all of them apply, consider shifting to a server based solution: Performance. Would a client based solution be noticeably slower than a server-based one (including traffic)? Javascript is fast nowadays, but a computationally expensive algorithm might require ...



Top 50 recent answers are included