RE: [PEAR-DEV] Re: [Patch] SOAP content type change for mime attachments

Zitat von xo@dogsonacid.com:

Moaning that other people's software is broken doesn't help if you have no power to fix it. Perhaps the functionality of this patch should be made user-selectable (off by default)?

No, as I said, this is one of the most basic formats used in the internet. It's used with every email sent, and every web page requested. If an software isn't able to handle this properly, I don't want to know what else it isn't able to handle.

-----Original Message----- From: Jan Schneider [mailto:jan@horde.org] Sent: 06 February 2006 22:58 To: pear-dev@lists.php.net Subject: [PEAR-DEV] Re: [Patch] SOAP content type change for mime attachments Zitat von "Huckey, Michael" <Michael_Huckey@adp.com>:

When sending attachments to various other soap implementations that conform to WS-I attachment standards, a simple fix to the content type will allow Mime attachments to work with these other vender implementations. Without this change failures occur when sending to these vendor's products. It appears that this format is widely accepted as correct among various venders and does not cause any adverse affects to the existing PEAR SOAP package. Although several other changes would also be desirable to bring this package up to WS-I standards, all other requirements can be met by the current package so this is the only one I have addressed in this patch.

Are you kidding? This is basic Content-Type header specification like being used for decades. Even the WS-I specs use that format in their examples. Any software not understanding the type attributes without the quotes is *badly* broken. Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting/ -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting/