 |
 |
 |
>-----Original Message-----
>From: Bullard, Claude L (Len) [mailto:clbullar@i...]
>Sent: Monday, February 02, 2004 2:16 PM
>To: Dare Obasanjo; Michael Champion; XML DEV
>Subject: RE: [xml-dev] best practice for providing newsfeeds ?
>
>At the same proportions in the mix?
>
>I've no dog in this game, but the patterns are fascinating.
>It's fun to figure out which are the stable food fights and
>which are chaotic. If it is indeed customer pull, and the
>customers are stronger than the technologists, I would expect
>a stable pattern of new features in the software releases and
>reasonably happy customers. The trick is to find the coupler
>between the two feedback sources. Namespaces don't ever seem
>to make any customers happy, so I doubt that is it.
If your customers are XML geeks I'd expect not. If your customers are
reqular people who just want software to work then they are just an
implementation detail.
--
PITHY WORDS OF WISDOM
The heaviest burden a man can carry is a chip on his shoulder.
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |