Store options in database or in a file? -


In the client-server database application,

, the different options where the customer needs to read from the server, where will you store them? In the database or in some files that will then be transferred to the network, or there is no better way.

It depends on the specific.

Generally speaking, there is very little to store some things in a file on the server while speaking (except for images, videos, songs etc.) databases.

If you are storing, say, customer preferences you can store them in a file in the client, but it has portability issues (which do not have profile settings on the other pc with the user ) But this may be appropriate if the client "offline" can be used.

Perhaps the best of both worlds is to store things in a database on the server and allow them to cache on the client (perhaps in the file) to allow offline use, if they have an app in question is applicable.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -