New answers tagged

0

The architecture you described is pretty common so far, I think you are missing just one thing: In case that your app and your backend reside on different domains, you can't use cookies any more to store the token. The typical process would be: user posts credentials via app to backend, backend creates a token, app stores the token in localstorage. On every ...


0

It doesn't. When your IP address changes to Y, the response never reaches your LAN. So why don't you notice IP address changes? Because it doesn't happen too frequently. At home, your IP should change at most once per day. Because requests are very fast. Once you press Enter after you typed “google.com,” the response reaches your PC in dozens of ...


0

As an abstract exercise, this is no different than controlling access on the public internet. Your application will need to do some form of authentication and authorization for parts of it that require limited access. It sounds like you are concerned about employees in the company having access to the server itself the application is on to change things. ...


-2

The proper way is return 404 when the path is wrong. REST is just plain wrong when it comes to using response codes in general and 404 in particular. Keep a separation between you code and the webserver, return a result or throw an exception and let the webserver decide what the response code should be. Generally this means returning 200 and json in the ...


0

Answering my own question, a Windows Service looks appropriate here. And .Net Core supports running under it with a Nuget extension. Here's a how to article: https://dotnetcoretutorials.com/2018/09/12/hosting-an-asp-net-core-web-application-as-a-windows-service/. @Theraot thanks for your answer, however a Windows Service is preferable as it works out of ...


0

Multiple ways to skin the cat! Depends if you want to utilize Encryption capabilities within a DB, or application (server-side) encryption capabilities before persisting in DB. Some vendors provide encryption add-ons, modules that allow you to configure (including the keys) the DB to keep all data at rest in encrypted form. Alternatively, you can implement ...


2

We could debate the design of the 404 code and perhaps you could devise some way to differentiate no resource found at a valid path branch. I think though, when you start thinking about other scenarios, this isn't straight forward. What about a URI where the resource is defined by multiple parts of the path that may or may not exist? For example, you ...


0

The following makes sense: and application that launches an standalone web server alongside to a browser pointing to it. Then the application can hide, perhaps placing an icon in notification area to allow to stop the server. The application may also monitor the server for crashes, backing up logs and restarting the server if needed. And yes, that same ...


1

I'm not sure if this completely meets your needs but I think one thing that could be fairly simple to implement here is to give each part of your model its own URI. That is, every node of the tree would have reachable via a unique endpoint. You could derive the naming from the tree or use e.g. a hash. It doesn't really matter as long as these are uniquely ...


3

It took a couple of readthroughs to verify I had a good understanding of where you're coming from and what you're trying to do, and I think I get it. It sounds like you're in the middle of the foundational design phases of a large-scale practical research project, and are building out this system's base framework. It is very cool to see the amount of ...


Top 50 recent answers are included