[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] Why xml for the manifest file ?
- From: Sankar P <sankar.curiosity@xxxxxxxxx>
- Date: Fri, 17 Jul 2009 17:40:01 +0530
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=ZE6Lvd4pCep6K+ovyHfsuQE+iH+KK0dSYgaQJYFEaY0dO2kkoY/swyoZXxGXl32UHN hvmNZ4zGZlHRkHLAUXSzTwFvghoaMZRQHHBjM1UiJrFDd7bss+aPcXIqhD9VOo8ZrfZU mxsk8tCggD6gD9HhizxHGn2AJ1sc06K+ckNLs=
I am trying to design a software based on plugins-based architecture.
So I looked at eclipse to see how to go about this.
I would like to know what is the reason behind choosing xml as the way
for writing the plugin manifest file. An .ini file kind-of
configuration is much simpler to write and is cheaper to parse. One
reason that I could think of is, to check for mandatory elements (like
say plugin-id) which can be easily compared by checking against a
So, can someone explain me why XML is chosen and how it is beneficial
over a simple text file ?
I am not subscribed to the list and so please add my address
explicitly in your replies. Thanks.