Project Clarification Board for Simple Desktop Application - Business Partner by 
xhenxhe 
| From | Message |
 wyorks 07/17/2006 7:37 am EDT |
Hi,
As regards the desktop application, what sort of storage requirements do you have, e.g. do you require a database backend or something altogether simpler like a flat file system? How much data are you anticipating will be stored ? |
| xhenxhe 07/17/2006 7:46 am EDT |
I think a database would be overkill for this application. Though, sqlite would be fine. Flat files would be fine. XML would be fine. I guess whatever is easiest. It just seems it would be more work to deploy a database. |
| wyorks 07/17/2006 9:30 am EDT |
Thanks for the speedy response!
If the volume of data that you're dealing with is relatively small then a flat file would probably be the easiest solution for a number of reasons: 1) No db reads/writes required - most of the work could be carried out in memory (if the dataset is small enough) or through memory mapped files; 2) No need to parse xml 3) No need to have a database running and taking up system resources. SQLite is also an option, particularly if you forsee the dataset growing with time.... At the end of the day it's your call - I can but put accross my point of view ;) |
 debzequke 07/17/2006 3:47 pm EDT |
True, Flat file does not have database overhead but it lacks flexibility. Instead XML crucially differs from plain text in that it allows you to structure your data in a standard manner. This is important -- it means that other systems can interpret your XML, which is not as easily achievable in plain text. This describes what is meant by "interoperable file format" -- once you produce an XML file, it is open to everyone. An input, and all the information required to understand the structure of your data, is included in the file.
The key thing in XML is that it detaches the user interface or presentation from the structured data, which makes the process of integration of data from diverse sources and the manipulation of the data simple. One prominent positive of XML in .NET Framework is its compliance with the W3C recommended standards of XML, Namespaces, XSLT, XPath, Schema, and the Document Object Model (DOM). Also Microsoft .Net has also thrown in a few XML parsing widgets that are easier to use and that perform better than the XML DOM. I personally feel for many tasks that involve data, Xml is a good choice if not ADO.Net. If necessary when size and time matters XML in the .NET Framework would be easy extensible to ADO.Net. |
| wyorks 07/18/2006 4:53 pm EDT |
debzequke, good point and agree totally about the flexibilty that XML offers in terms of sharing data between systems and allowing the data to be used across applications and platforms, etc. The fact is though, IF the app is structured in the correct fashion it should be very easy easy to substitute the flat file functionality with XML functionality.
Having the app out and available quickly with a flat file format then allows more time to consider whether XML is the right way to go and if so whether to use custom software, freeware or to buy additional components in order to work with XML. |
| debzequke 07/18/2006 9:34 pm EDT |
There's no need for any additional components to employ Xml as there is rich builtin support in .Net Framework. Moreover Xml would not drag time instead it would speed up both the time required to design and implement systems based on object-oriented, in the sense of being suitable for describing objects of the real world or any abstract problem domain by modelling their properties as they are. Xml already provides access to a plethora of technologies for validating , manipulating, structuring, transforming and querying data. Specializing this project XML would do more than just as a text format for describing documents: Powerful abstractions like the XML Information Set open the door to processing non-textual data, such as having richer content, that is it can easily manage features like email, hypertext links, scrapbooks, image galleries, sounds, videos and including geographical aspects of the relationship between the family members using XML technologies. In genealogical models many have already started using GEDCOM/XML rather than the traditional GEDCOM. With Xml standards including the LDS church with GEDCOM XML, Gentech, GeniML and any others, it can be easily used in any genealogical applications to easily create, exchange, provide and analyze the informations. Also with recent advent of XLinq, modernized in-memory XML programming API designed to take advantage of the latest .NET Framework language innovations, why lack behind? |
| wyorks 07/19/2006 3:59 am EDT |
I don't believe it's "lagging" behind. Most of the programming I do, especially in my current role, must be platform independant and as a result I always look for alternatives to the the Microsoft way, hence the need to look around for alternatives.
You also don't need to explain the benefits that XML offers - I'm fully aware of them. |
 vhtmg108 08/30/2006 3:31 pm EDT |
i wasn't invited that project,but i really want to work in this project.(write in Java and prefer XML) |
If you would like to post a message to the project clarification board for Simple Desktop Application - Business Partner, please sign in.
What is Nerdlance.com?
Nerdlance.com helps webmasters, web designers, programmers, software developers, and business owners complete their much needed projects. After registering you may elect to pay for services, get paid for your services, or both!
A Nerdlancer is simply a freelancer. A freelancer is a person who sells his services to a company without a long term commitment or contract. Outsourcing allows you to get jobs completed without having to hire staff.
We have freelancers and project outsourcers from the following countries:
Afghanistan, Albania, Algeria, American Samoa, Andorra, Angola, Antarctica, Antigua and Barbuda, Argentina, Armenia, Australia, Austria, Azerbaijan, Bahrain, Bangladesh, Barbados, Belarus, Belgium, Belize, Bhutan, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, British Indian Ocean Territory, Bulgaria, Cambodia, Cameroon, Canada, Central African Republic, Chile, China, Colombia, Congo, The Democratic Republic of The, Costa Rica, Cote D'ivoire, Croatia, Cuba, Cyprus, Czech Republic, Denmark, Dominican Republic, Ecuador, Egypt, El Salvador, Equatorial Guinea, Estonia, Fiji, Finland, France, French Guiana, Gambia, Georgia, Germany, Ghana, Greece, Greenland, Guadeloupe, Guatemala, Guinea-Bissau, Haiti, Holy See (Vatican City State), Hong Kong, Hungary, Iceland, India, Indonesia, Iran, Islamic Republic of, Iraq, Ireland, Israel, Italy, Jamaica, Japan, Jordan, Kenya, Kiribati, Korea, Democratic People's Republic of, Korea, Republic of, Kuwait, Lao People's Democratic Republic, Latvia, Lebanon, Liberia, Libyan Arab Jamahiriya, Lithuania, Luxembourg, Macedonia, The Former Yugoslav Republic of, Madagascar, Malawi, Malaysia, Marshall Islands, Martinique, Mauritius, Mexico, Micronesia, Federated States of, Moldova, Republic of, Monaco, Mongolia, Morocco, Myanmar, Namibia, Nepal, Netherlands, Netherlands Antilles, New Caledonia, New Zealand, Nigeria, Norfolk Island, Northern Mariana Islands, Norway, Oman, Pakistan, Peru, Philippines, Poland, Portugal, Qatar, Romania, Russian Federation, Saint Helena, Saint Lucia, Sao Tome and Principe, Saudi Arabia, Senegal, Serbia and Montenegro, Sierra Leone, Singapore, Slovakia, Slovenia, Solomon Islands, Somalia, South Africa, South Georgia and The South Sandwich Islands, Spain, Sri Lanka, Sudan, Suriname, Sweden, Switzerland, Syrian Arab Republic, Taiwan, Province of China, Tajikistan, Tanzania, United Republic of, Thailand, Togo, Tokelau, Tonga, Trinidad and Tobago, Tunisia, Turkey, Turks and Caicos Islands, Uganda, Ukraine, United Arab Emirates, United Kingdom, United States, Uruguay, Uzbekistan, Vanuatu, Venezuela, Viet Nam, Virgin Islands, British, Virgin Islands, U.S., Zambia, Zimbabwe and Åland Islands.
Check us out on: Google,
Yahoo!,
MSN &
Open Directory Project (DMOZ)
