New answers tagged

0

In the interest of making information available to anyone in the future, my current solution is having a socket.io server running, which connects over a socket to a python script. the socket.io server just relays information between the two and is capable of handling multiple clients whereas a python only solution would not handle multiple clients without me ...


1

If you are using a database which supports transactions, then just upload the components in the same transaction. They won't be visible to the application until the transaction is committed, which will be an atomic event. Search for "database ACID" for more details. Alternatively, ensure all the resources for the page are in place before adding the HTML ...


0

Associate the token with the source IP address of the request in addition to the username when saving it to redis and when looking it up while authenticating a request. Remember to handle the case where you have a cookie but it doesn't match the token associated with the request's source IP address, authentication should fail in that case.


2

If you do not mind recompiling your code, I recommend you to look at TypeScript, developed by Microsoft. It has a C#-like syntax and is a supertype to pure JavaScript, which is compiled to it. Other than that, in combination with modern JS many modern IDEs, I have had a great experience with WebStorm by JetBrains (though it is very likely other IDEs support ...


2

A few assumptions: Microservices can communicate between themselves Implementations of each microservice are not relevant to the external world (this is even easier when abstracted into a container) Imagine a client/server interaction, the client/server might communicate with a JSON API. Or a message broker. The specific implementation does not matter, ...


0

PHP is a programming language. You use a web-server like Apache to handle HTTP requests and depending to your settings your web-server runs PHP in the background. Node.js is an environment to run JavaScript. JavaScript is the programming language that you are building your stuff on it. Here Node.js is your web-server that handles HTTP requests. Node.js ...


1

I think it's quite alright to just bump your patch version component if you want to make a new package with no changes other than additional tests. In a way you've just improved your "documentation" a bit.


3

I think you're overthinking it. Look at it from the perspective of the user of your package, upgrading. Is it safe for them to do with no code changes? Then bumping the 'z' version of x.y.z is entirely appropriate. The alternative here is to not release an updated version at all, since you can't (or shouldn't be able to) release new code that has the same ...


0

So the biggest reason for choosing to use RabbitMQ over Redis is the failure scenarios, and clustering. This article really explains it best, so I'll just provide the link: https://aphyr.com/posts/283-jepsen-redis Redis sentinel and more recently redis clustering are not able to handle a number of very basic failure scenarios that made it a bad choice ...


0

If you mean that they should be able to import their existing files, then you will have to create a mapping to translate each of the existing Amazon, Newegg, ... formats into your database. For XML feeds that means mapping XPath expressions to your columns. For flat file feeds it means mapping the headers in the flat file to your database columns.



Top 50 recent answers are included