From: Siddhesh P. <sid...@gm...> - 2010-07-31 07:14:04
|
On Sat, Jul 31, 2010 at 7:50 AM, kay <ka...@gm...> wrote: > If library do the work, then library should give the chat room information > to client to show it in its own way. > And client must know the data structures used in the library in order to > traverse the list. Is this a good way? Currently we're exposing the xml to the client to parse and do whatever it wants with it. Additionally it would be nice if we define some structures (some kind of a list) that store and present this information. We can then deprecate the xml in a future release since it is likely that the xml may change over time and we would want to protect the client implementation from this change. > I just took a look at the YIM API and didn't find any information about > chat room. To use the Y!M API, you will need to do a lot of porting; that probably won't be feasible as part of your project scope. But yes, it probably needs to be done in the future. Has anyone been able to decipher the developer agreement to see any problems? I haven't had the time to look at it recently. -- Siddhesh Poyarekar http://siddhesh.in |