Jamin W. Collins wrote: >I've been wondering for a while now, why there isn't a central >abstracted ICQ communication library for the various ICQ clients? > >It seems that it would make more sense for the various client developers >to coordinate on a central abstracted library that they could all >benefit from, rather than each working to implement redundant >functionality separately. > >Then each project could link to the library in more generic ways and >changes to the protocol would possibly only mean changes to the core >library leaving clients largely unaffected. > >>From what I've seen, LICQ and GnomeICU seem to be two of the most >advanced ICQ clones available. Combined effort from these two projects >would most likely result in a very useful core library. Has anything >like this been looked at? > The biggest problem is to have everyone agree on using the same language. Then after the language settled we have to define the API as well. This could take a long time but we could all benefit from it if it can really happen.
As Olivier mentioned there are stuffs that is not easy to seperate (but not impossible). But this could create more burden in defining a common api that can satisfy all parties. I would love to join force in doing that as long as it is not in C++, because gnomeicu is a C client :) How about the LICQ team, what do you guys think? (we know icq protocol is keep changing, the only way to have full support (to keep up with the changes) for it is to have more developer to work on it) Patrick > >Jamin W. Collins > > >_______________________________________________ >gnomeicu-support mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/gnomeicu-support > _______________________________________________ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
