Tag Info

New answers tagged

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 ...


1

If time is of the essence, then I suggest to look to hire somebody to do it. You could find somebody on freelancer or other similar site. You could ask that they explain you why they did what they did so you learn something. Plus you'll have the code. If you decide to go on your own, which I don't recommend, I would go for AWS using nodejs + expressjs. You ...


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 ...


0

Django will help you in that manner. You will redirect multiple sites to your Django instance, and the Django instance will use the API that can help you with saving through economies of scale, with VM costs/ API subscription costs, etc. In this context, I am assuming that you are not using limited free tiers, or you do not have complicated SLAs with your ...


1

I couldn't convince my boss yet that this is a bad idea, am i wrong here? I feel like a web app is not the right tool for this job. And if this is indeed a bad idea, what would the best way be for me to clearly explain him that? I am really not sure this is a bad idea. To me it sounds like a good idea because your customers will get what they want ...


1

First rule of thumb - never start over if you can avoid it. That's a Joel Spolsky rule of software development. So that's automatically a strike against re-writing your app in HTML5. Fortunately, you really only have to re-write the client. You can update the server app incrementally, but you don't need to replace it wholesale. However, moving from ...


0

You can have a lean, lightweight app and still have a rich object model. If you're using Angular, that means you're probably writing a single-page application and driving the UI from web services. Those web services should provide you with the data you need for the UI. On the server, you can have a data model and application layer as complex as your ...


0

One should only resend once there is proof of delivery failure. Some email providers use a period of time to attempt to deliver the email. A typical the default is 48 hours. Over this 48 hour period they may attempt to deliver the email N number of times, where N could be 8, 10, etc. This is done to help on transient email errors. For example, what if ...


1

Yes, it is quite possible, and I have done such myself. The situation I was in was deployment of a large .war file. The web application part of it was not that big - but it also contained within it a Java Web Start application. The combined size of all of this was a few hundred megabytes. This posed a problem for deployment - when pushing all of this down ...


2

Yes. It is possible to patch a JAR file using jar -u. It is also possible to patch a WAR file the same way. But I would NOT recommend it. The JAR or WAR file should be the unit of deployment / management. If you start patching JAR / WAR files on production servers, it is hard to track what is actually being used where. If you are not careful, chaos and ...


0

For a 3-tier architecture you are (partly) trying to scale. This means that you will offload some of the processing from the single database to a few application servers, and offload processing from them to many web servers. This also allows you to write code for each tier that is specialised, so the DB server will only run the DB, the app servers will only ...



Top 50 recent answers are included