libxode  
about   -   docs   -   get   -   faq   -   sf project page

faq (frequently asked questions)

  1. General Quesions
    1. What is libxode?
    2. How do you pronouce libxode?
  2. Jabber Related Questions
    1. What does libxode have to do with Jabber?
    2. Why release a different version of libxode?
    3. How does this libxode differ from the Jabber Project's libxode?
    4. Will my code still work if I used Jabber's libxode?



1. General Questions
1a. What is libxode?

libxode is a library which proveds convenience files for dealing with Memory pools, XML and strings.

1a. How do you pronounce libxode?

The developers tend to pronounce it lib - zode

2. Jabber Related Questions
2a. What does libxode have to do with Jabber?

libxode was first created specifically for the Jabber Project, and is currently used internally in the Jabber server, and some of the Jabber clients.

2b. Why release a different version of libxode?

The Jabber version of libxode had many Jabber specific function calls in it. This version cleaned out all those calls, and turned it into a XML-, pool-, and spool-only library.

2c. How does this libxode differ from the Jabber Project's libxode?

Any Jabber specific code was taken out of the libxode library, and all functions were renamed for library cohearance. all xmlnode_*() function calls were renamed to xode_*() calls, all pool_*() calls renamed to xode_pool_*(), all spool_*() calls renamed to xode_spool_*(), and all xstream_*() calls renamed to xode_stream_*(). In addition, constants, and #define symbols were renamed to XODE_*. This helps to identify function calls that are located in that library.

2d. Will my code still work if I used Jabber's libxode?

No, all of the symbol names have changed (see question 2c), and are no longer compatible.

 
 
Contact info:   Chris Moyer  or  Keith Minkler SourceForge Logo