Charlie Savage wrote:
>> In XMPP4R we're bound to the very intuitive REXML API because that's
>> what XMPP4R is about: dealing with XML. I thought the only way out
>> would be resembling it. That's why I have started REXML-dropin, a
>> wrapper around libxml:
>> http://github.com/astro/rexml-dropin/
Hi Stephan,
In XMPP4R we're bound to the very intuitive REXML API because that's
what XMPP4R is about: dealing with XML. I thought the only way out
would be resembling it. That's why I have started REXML-dropin, a
wrapper around libxml:
http://github.com/astro/rexml-dropin/
Curious how is pr
To be honest, I'm not convinced by libxml-ruby's code, but it looks
way cleaner than REXML. So far, I'm able to run a basic XMPP client
with it. There's a lot left to be done, so go ahead and fork it!
All suggestions on improving libxml-ruby are of course
appreciated...Some of the things that I
Are you tired of strange REXML behaviour? Do you need twice the
performance when dealing with XML? Are you stuck with the REXML API
because your code uses it everywhere? You're not alone.
I've long fantisized about this day. Nice work! This'll likely bring
additional eyes to the code too, ve
