The shared white board and file transfer thread looks to me like we need a more generic session protocol which is capable of doing
1) Whiteboard 2) File transfer 3) Voice/ Video 4) chat and MUC mostly based on the <message> than <iq> ( it looks the core requirement is to "work with with the message session" ) and able to accommodate new services comes up. It should be able to add /remove participants and able to do push at required stages. reason why i think so: we need new extensions for managing session and we are brainstorming for that. Final out put can be one xep for generic framework protocol and contents and transports or one xep for every service ( means white board, file transfer etc etc ) . The later makes really complicated and tough to implement. thanx unni On 9/14/07, Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > > Matthew Wild wrote: > > On 9/13/07, *Tobias Markmann* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Exactly. You can't expect an IM client to handle transfers of CD or > > DVD image sized files. For these large files protocols like > > BitTorrent have been developed and work really nice on doing that. > > > > > > I found myself receiving a file over 200MB only yesterday, simply > > because it was the easiest way to do it. Protocols like BitTorrent are > > more for publishing files, than direct file transfer. > > > > I don't see why it is *necessary* for the protocol to place a limit on > > file size at all, barring technical (implementation?) restrictions. > > I'm not saying that "the" protocol needs to limit the file size. I'm > saying that we need to think about how to handle different file sizes, > since the size of the file may have an impact on the choice of file > transfer method (e.g., you may want to send really small files via IBB > but not really big files). > > Peter > > -- > Peter Saint-Andre > https://stpeter.im/ > > >
