The file format that is currently used to hold buddylists is one that I have always hated, but that I adopted to keep up compatibility with the non Java version of Everybuddy. Now that it's obvious that the Everybuddy guys aren't really interested in this, and that this is going a seperate way, I'd like to go ahead and get rid of it.
So, anyone want to make suggestions as to the new format? Perhaps GROUPNAME:BUDDYNAME:SERVICEID:USERNAME one per line with colons escaped with other colons?
The other config files (which need to be implimented also) could be in a similar format...
~Chris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I never quite understood why people want to use XML in configuration files. From the discussions I've heard, it's basically just a buzzword, using XML just for the sake of using it.
Since the buddylist files are never intended to be seen by anyone other than the server itself, it seems strange to write it in a form any more complex and extensible than it needs to be.
Since you recommend it strongly... why? :)
~Chris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
XML is a reasonable standard with good libraries in multiple languages.
"Since the buddylist files are never intended to be seen by anyone other than the server itself, it seems strange to write it in a form any more complex and extensible than it needs to be."
1. Others will see it. Any time you think nobody will - you're wrong. Someone will want to write an arbitrary tool in an arbitrary language that cleans it up/modifies it/whatever.
2. The format will change (extend). XML makes this transition easy. Someone will want to add another server/tool that reads the same file and wants to add some information. Or they will decide to use another language for the server and wish they didn't have to write another damn parser for your magic file.
3. Folks will want to import/export it.
This has all happened countless times in the past - let's not repeat the mistakes. XML might be a buzzword, but so is html, applet, and Java. XML is at least a well defined and useful one...
Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The file format that is currently used to hold buddylists is one that I have always hated, but that I adopted to keep up compatibility with the non Java version of Everybuddy. Now that it's obvious that the Everybuddy guys aren't really interested in this, and that this is going a seperate way, I'd like to go ahead and get rid of it.
So, anyone want to make suggestions as to the new format? Perhaps GROUPNAME:BUDDYNAME:SERVICEID:USERNAME one per line with colons escaped with other colons?
The other config files (which need to be implimented also) could be in a similar format...
~Chris
My only (and strong) recommendation: use XML.
I never quite understood why people want to use XML in configuration files. From the discussions I've heard, it's basically just a buzzword, using XML just for the sake of using it.
Since the buddylist files are never intended to be seen by anyone other than the server itself, it seems strange to write it in a form any more complex and extensible than it needs to be.
Since you recommend it strongly... why? :)
~Chris
XML is a reasonable standard with good libraries in multiple languages.
"Since the buddylist files are never intended to be seen by anyone other than the server itself, it seems strange to write it in a form any more complex and extensible than it needs to be."
1. Others will see it. Any time you think nobody will - you're wrong. Someone will want to write an arbitrary tool in an arbitrary language that cleans it up/modifies it/whatever.
2. The format will change (extend). XML makes this transition easy. Someone will want to add another server/tool that reads the same file and wants to add some information. Or they will decide to use another language for the server and wish they didn't have to write another damn parser for your magic file.
3. Folks will want to import/export it.
This has all happened countless times in the past - let's not repeat the mistakes. XML might be a buzzword, but so is html, applet, and Java. XML is at least a well defined and useful one...
Kurt