I've been thinking recently about the future of XMLSP.
I wrote XMLSP for my private use (I think it was for my multiprotocol p2p client as a configuration manager). I didn't pay much attention about readable code or commenting, I just wanted it to work. After few days, I decided to release the code with hope it will be usefull to someone else.
I didn't thought it will be downloaded 1500 times, but that just happend. I think it's time to clean all the stuff I was too lazy to do.
Since there are no more bug reports about runtime stuff, only compile time errors/warning, this is what I will focus on for 1.0 release.
I will also clean the problem std::string and const std::string& argument passing.
Since I initialy wrote it, I've been using Java at work and I started to like Java naming convention. Also, xml and xml dom parsers are not thread safe. The error code and error messages may be lost when many threads parse XML at the same time.
I will make the following changes in version 2.0:
- Java naming convention (onError() instead of on_error())
- DOMElement::loadXML will be in a separate object
- new DOMElement types, for comments, processing instructions, doctypes and cdata (parent tag element will assemble cdata from DOMCDataElement objects)
If you have any ideas for the new XMLSP, please post them here.
I hope I will soon post the new interface on this forum.
And I one licensing question. Which license do you think would be best for XMLSP ? MIT, BSD or public domain ? I wrote XMLSP because I didn't liked GPL and LGPL so I won't use them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've been thinking recently about the future of XMLSP.
I wrote XMLSP for my private use (I think it was for my multiprotocol p2p client as a configuration manager). I didn't pay much attention about readable code or commenting, I just wanted it to work. After few days, I decided to release the code with hope it will be usefull to someone else.
I didn't thought it will be downloaded 1500 times, but that just happend. I think it's time to clean all the stuff I was too lazy to do.
Since there are no more bug reports about runtime stuff, only compile time errors/warning, this is what I will focus on for 1.0 release.
I will also clean the problem std::string and const std::string& argument passing.
Since I initialy wrote it, I've been using Java at work and I started to like Java naming convention. Also, xml and xml dom parsers are not thread safe. The error code and error messages may be lost when many threads parse XML at the same time.
I will make the following changes in version 2.0:
- Java naming convention (onError() instead of on_error())
- DOMElement::loadXML will be in a separate object
- new DOMElement types, for comments, processing instructions, doctypes and cdata (parent tag element will assemble cdata from DOMCDataElement objects)
If you have any ideas for the new XMLSP, please post them here.
I hope I will soon post the new interface on this forum.
And I one licensing question. Which license do you think would be best for XMLSP ? MIT, BSD or public domain ? I wrote XMLSP because I didn't liked GPL and LGPL so I won't use them.