Sure its a big problem, but it is a client problem, the current unoffical standard or sending files is via the HTTP protocol, if a client with file transfer does not work correctly email the author and tell them so, thats the only way things are going to get fixed.
Richard ----- Original Message ----- From: "Andy Beetz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 06, 2002 11:38 AM Subject: Re: [JDEV] File transfers > I just performed a quick test on the client interoperability with regards to > file transfers and here is what I found > > Setup: > Jabberd server > myJabber client > Winjab client > > > Attempt to send a file from myJabber client to Winjab client: > The receive dialog popped up, hit receive. The file was created but > no data was transferred. > > Attempt to send a file from Winjab client to myJabber client: > Receive dialog popped up, hit receive. Immediately a error msg is > shown (on myJabber client) > 'Run-time error '380': Invalid property value', clicked ok, the > myJabber client acc vio'd and died. > > To me this is unacceptable, to have lots of available clients which can't > communicate correctly with one another. I just see the same thing happening > as did with MIME, where everyone interpreted the RFC's in their own way, and > now we are left with exploits left right and centre because of > inter-operability 'fixes'. > > Let me know what you think > > > -------------------------------------------------------------------------- ------------------------------------- > Clearswift monitors, controls and protects all its messaging traffic in > compliance with its corporate email policy using Clearswift products. > Find out more about Clearswift, its solutions and services at > www.clearswift.com. > **************************************************************************** ******* > This communication is confidential and may contain privileged > information intended solely for the named addressee(s). It may not > be used or disclosed except for the purpose for which it has been > sent. If you are not the intended recipient, you must not copy, > distribute or take any action in reliance on it. Unless expressly stated, > opinions in this message are those of the individual sender and not of > Clearswift. If you have received this communication in error, please > notify Clearswift by emailing [EMAIL PROTECTED] quoting the > sender and delete the message and any attached documents. Clearswift > accepts no liability or responsibility for any onward transmission or use of > emails and attachments having left the Clearswift domain. > > This footnote confirms that this email message has been swept by > MIMEsweeper for Content Security threats, including computer viruses. > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
