RE: content-wire feeds riddle help

"Nick Lothian" <[email protected]> Tue, 4 Oct 2005 13:13:36 +0930
Newsgroups gmane.network.syndication.discuss
Message-ID <[email protected]>
------_=_NextPart_001_01C5C895.CD3C8BEC
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

You mean the <META NAME=3D"ColdFusionMXEdition" CONTENT=3D"ColdFusion DevNe=
t
Edition - Not for Production Use."> tag?
=20
I would guess that using a licenced version of ColdFusion might help
with the "Not for Production Use" problem....


________________________________

	From: [email protected]
[mailto:[email protected]] On Behalf Of Content-wire Research
	Sent: Tuesday, 4 October 2005 1:09 PM
	To: [email protected]
	Subject: [syndication] content-wire feeds riddle help
=09
=09
=09=20
	  Hi good syndication peoples
=09=20
	you ll remember content wire, we started off about 5 years ago
and several of you helped us pull our rss feeds together
=09=20
	this happened in a variety of fashions, from spiders scraping
html and converting to rss, to various other types of feed burners and
news aggregators that you guys have been working on
=09=20
=09=20
=09=20
	a couple of years later our software supplier created a built in
feature to produce feeds, that we have been using ever since, in fact
moreover, google, newsnow, factiva and various others use our feeds
daily
=09=20
	it turns out that our rss does not validate now due to a
coldfusion propretary tag at the top, and this is preventing=20
	some of our users who are able to write ad hoc parsers to use
our feeds
=09=20
	nobody ever told me that was a problem before, and considering
our feeds code is embedded in the system, it is not likely that i ll be
able to upate the code until next upgrade
=09=20
	first, I d like to ask all on this list who have worked with
content-wire rss before to kindly look into the problem
	and update their entires where relevant, we have changed our
feeds structure=20
=09=20
	second, if someone can suggest a quick fix (I am thinking of
options)  other than changing the code
	that would be appreciated, thanks
=09=20
	www.content-wire.com/feeds/feeds2.cfm
=09=20
=09=20
	Paola=20
=09=20=20
=09
________________________________

	YAHOO! GROUPS LINKS=20


=09=09
	*	 Visit your group "syndication
<http://groups.yahoo.com/group/syndication> " on the web.
=09=09=20=20
	*	 To unsubscribe from this group, send an email to:
		 [email protected]
<mailto:[email protected]?subject=3DUnsubscribe>=20
=09=09=20=20
	*	 Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service <http://docs.yahoo.com/info/terms/> .=20


________________________________

IMPORTANT: This e-mail, including any attachments, may contain private or c=
onfidential information.=20
If you think you may not be the intended recipient, or if you have received=
 this e-mail in error,=20
please contact the sender immediately and delete all copies of this e-mail.=
 If you are not the intended=20
recipient, you must not reproduce any part of this e-mail or disclose its c=
ontents to any other party.

This email represents the views of the individual sender, which do not nece=
ssarily reflect those of=20
education.au limited except where the sender expressly states otherwise.

It is your responsibility to scan this email and any files transmitted with=
 it for viruses or any other=20
defects.

education.au limited will not be liable for any loss, damage or consequence=
 caused directly or indirectly by this email.


------_=_NextPart_001_01C5C895.CD3C8BEC
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii"><BASE 
href="file://C:\Program Files\Common Files\Microsoft Shared\Stationery\">
<META content="MSHTML 6.00.2900.2722" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff background=file://C:\Program signature.gif 
Shared\Stationery\ Files\Microsoft Files\Common NOSEND="1">


<DIV dir=ltr align=left><SPAN class=973244203-04102005><FONT face=Arial 
color=#0000ff size=2>You mean the &lt;<SPAN class=start-tag>META</SPAN><SPAN 
class=attribute-name> NAME</SPAN>=<SPAN 
class=attribute-value>"ColdFusionMXEdition" </SPAN><SPAN 
class=attribute-name>CONTENT</SPAN>=<SPAN class=attribute-value>"ColdFusion 
DevNet Edition - Not for Production Use."</SPAN>&gt; tag?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=973244203-04102005><FONT face=Arial 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=973244203-04102005><FONT face=Arial 
color=#0000ff size=2>I would guess that using a licenced version of ColdFusion 
might help with the "Not for Production Use" problem....</FONT></SPAN></DIV><BR>
<BLOCKQUOTE 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
  <HR tabIndex=-1>
  <FONT face=Tahoma size=2><B>From:</B> [email protected] 
  [mailto:[email protected]] <B>On Behalf Of </B>Content-wire 
  Research<BR><B>Sent:</B> Tuesday, 4 October 2005 1:09 PM<BR><B>To:</B> 
  [email protected]<BR><B>Subject:</B> [syndication] content-wire 
  feeds riddle help<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp; Hi good syndication peoples</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>you ll remember content wire, we started off about 5 years ago and 
  several of you helped us pull our rss feeds together</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>this happened in a variety of fashions, from spiders scraping html and 
  converting to rss, to various other types of feed burners and news aggregators 
  that you guys have been working on</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>a couple of years later our software supplier created a built in feature 
  to produce feeds, that we have been using ever since, in fact moreover, 
  google, newsnow, factiva&nbsp;and various others use our feeds daily</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>it turns out that our rss does not validate now due to a coldfusion 
  propretary tag&nbsp;at the top, and this is preventing </DIV>
  <DIV>some of our users who are able to write ad hoc parsers to use our 
  feeds</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>nobody ever told me that was a problem before, and considering our feeds 
  code is embedded in the system, it is not likely that i ll be able to upate 
  the code until next upgrade</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>first, I d like to ask all on this list who have worked with content-wire 
  rss before to kindly look into the problem</DIV>
  <DIV>and update their entires where relevant, we have changed our feeds 
  structure </DIV>
  <DIV>&nbsp;</DIV>
  <DIV>second, if someone can suggest a quick fix (I am thinking of 
  options)&nbsp; other than changing the code</DIV>
  <DIV>that would be appreciated, thanks</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>www.content-wire.com/feeds/feeds2.cfm</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Paola </DIV>&nbsp; 	<span style="COLOR: black">
	<font face="Times New Roman" color="black" size="2">
	<div>
		<strong>IMPORTANT:</strong> This e-mail, including any attachments, may 
		contain private or confidential information. If you think you may not be 
		the intended recipient, or if you have received this e-mail in error, 
		please contact the sender immediately and delete all copies of this 
		e-mail. If you are not the intended recipient, you must not reproduce 
		any part of this e-mail or disclose its contents to any other party.</font><font face="Times New Roman" color="black" size="2"><p>
		<font size="2">This email represents the views of the individual sender, 
		which do not necessarily reflect those of <strong><em>education.au 
		limited</em></strong> except where the sender expressly states 
		otherwise.</font></p>
		<p><font size="2">It is your responsibility to scan this email and any 
		files transmitted with it for viruses or any other defects.</font></p>
		<p><strong><em><font size="2">education.au limited</font></em></strong><font size="2"> 
		will not be liable for any loss, damage or consequence caused directly 
		or indirectly by this email.</font></font></div>
	</span></div>

  



</BODY></HTML>

------_=_NextPart_001_01C5C895.CD3C8BEC--