All geek questions in one place

Is Embed Resource a good read-only xml database approach?

I have an open source application ( here )

This application receives a character or sentence and provides some unicode information.

Unicode Unicode character database provided by Unicode.org is an XML document (130 MB)

At first I embed this XML in my DLL, but I don't know if this is a good approach or not. because the increase in size of the DLL is only due to this XML document. I can use it, like any other resources, but the user can see it.

What should I do? What is the best template for this? and why?

TIA

+3
source share
4 answers

I assume that an inline resource is a good option if you are happy to recompile and redeploy each time there is a change; also, just because you can be happy to do this does not mean that everyone will be :)

A very common approach is to abstract any kind of access to data behind the interface; if you do, you can let users choose which implementation they want (provided that you provide a pair), and this will allow them to write their own. In terms of patterns, this is Dependancy Inversion (also known as control inversion).

instansiation config ( : Factory), (, ). , , : XML , SqlLite, -/ ..

Rolands - ( , ).

Visual Studio.NET

+1

, XML . , . , dbs (, SQLite - ).

XML vs SQLite, : Xml Sqlite, Xml ?

+1

XML - . XML DLL, , XML. XML DLL? -, , -, , .

+1

, ? , , , XML-.

0
source

Source: https://habr.com/ru/post/1749395/

More articles:


All Articles