17 March 2005

XML Concepts: Using reverse-osmosis principles to allow private feeds to interact with external platforms

Should private feeds still have a way to integrate with external platforms? Of course, and this explains how to do it.


Test Results


This test looked at the integration between two generated feeds. One is the Newsgator online tool which automatically monitors a given URL; the second was a conversion tool which converts an RSS feed into HTML.

The Newsgator Feed and 2RSS tools independently work OK. For some reason, when we combine the two feed-tools into a single feed, we get several errors. At this juncture it is not clear what the issue is.

It appears as though both platforms independently comply with the specifications. What is interesting is that two-apparently compliant platforms do not integrate. This may be of interest to the FeedMesh.

Newsgator generated feed entered here yielding these results:


2RSS Report


Warning: fopen(http://services.newsgator.com/ngws/svc/RelatedRSS.aspx?fid=917): failed to open stream: HTTP request failed! HTTP/1.1 401 Unauthorized in /usr/www/users/drm/rss2html.com/rss2html.php on line 352

Warning: fread(): supplied argument is not a valid stream resource in /usr/www/users/drm/rss2html.com/rss2html.php on line 354

Warning: fclose(): supplied argument is not a valid stream resource in /usr/www/users/drm/rss2html.com/rss2html.php on line 357

Last Updated: 12/31/1969 07:00 PM

This page was created using RSS courtesy of FeedForAll


What is striking about the result is that both platforms have generally provided superior service, timely responses. Yet, these errors are not listed on either google or Technorati suggesting this is a new error related to something recently changed on 2RSS.

There could be a validation issue, which would raise the question with Newsgator: Is it possible the auto-generate tool is generate a feed that appears to be valid, but is actually not?

Actually, the problem appears to be related to the Newsgator permissions. If we validate feed, it doesn't work suggesting that the Newsgator URL for this particular URL-watch is only intended to be maintained on the Newsgator Online site.

In other words, at this point it appears as though there really isn't a problem:

  • Newsgator Online correctly reports content along this URL

  • 2RSS correctly reports the status of that content

  • Newsgator Online adequately prevents content on a private URI to be released


    LEGAL NOTICE


    Creative Commons License

    This work is licensed under a Creative Commons License.

    You may not copy any of this work to promote a commercial product on any site or medium in the universe.

    If you see this work posted on a commercial site, it violates the creative commons license; and the author does not endorse the commercial product.

    Free to use for non-commercial uses. Link to this original blogspot and cite as .


    The only way to view this URI appears to be if Newsgator Online were to adjust their settings allowing a private feed to be converted to something else. How Newsgator Online, or any aggregator for that matter, would be able to both maintain a private feed, yet allow that feed to be adjust by an external site remains to be understood.

    Perhaps there is a way. Anyone have any ideas?


    XML Osmosis

    Private feeds interacting with public forums


    Yes: Create a flexible firewall. One that is like an two-way reverse osmosis used for desalizating water.

    Although the feed may be protected, it still can pass through the membrane to interact with something else, all the while it still is protected.

    The trick would be to apply the lessons from osmosis in biology to the aggregators and the external platforms.


    XML Reverse Osmosis Modules


    The modules would be:

  • allow the firewall to exist;

  • break down the URI into a transportable code along the firewall;

  • reconstruct it at the external platform;

  • have it interact with the external platform;

  • capture the result in an external cache;

  • breakdown the newly created feed into something that can cross the barrier;

  • then recombined back into a valid feed or data that the originating platform would recognize as valid;

  • then re-accomplish the results to send back the confirming message back to the external platform that the URI was in fact, valid [even though it was protected].


  • The trick to make this work would be to have a method to integrate with an external platform in a way that accepted the URL-pseudo-code [after being broken down] in way that protected the code from outside review, but at the same time ensured the code was workable.

    How to make a code that can breakdown, interact, recombine, but still not be readable?

    If we go to our 1/2-code principle used in creating a two-way search engine, it would be possible to:

  • export only part of the original code;

  • let the external tool work on that portion, then

  • recombine the result with the other half.

    If another platform attempted to use the ejected code, it would never work because they didn't have the matching key, which only Newsgator would have.

    Presto! The private feed can now interact with a public platform, but still be private.
  • Should private feeds still have a way to integrate with external platforms? Of course, and this explains how to do it.


    Test Results


    This test looked at the integration between two generated feeds. One is the Newsgator online tool which automatically monitors a given URL; the second was a conversion tool which converts an RSS feed into HTML.

    The Newsgator Feed and 2RSS tools independently work OK. For some reason, when we combine the two feed-tools into a single feed, we get several errors. At this juncture it is not clear what the issue is.

    It appears as though both platforms independently comply with the specifications. What is interesting is that two-apparently compliant platforms do not integrate. This may be of interest to the FeedMesh.

    Newsgator generated feed entered here yielding these results:


    2RSS Report


    Warning: fopen(http://services.newsgator.com/ngws/svc/RelatedRSS.aspx?fid=917): failed to open stream: HTTP request failed! HTTP/1.1 401 Unauthorized in /usr/www/users/drm/rss2html.com/rss2html.php on line 352

    Warning: fread(): supplied argument is not a valid stream resource in /usr/www/users/drm/rss2html.com/rss2html.php on line 354

    Warning: fclose(): supplied argument is not a valid stream resource in /usr/www/users/drm/rss2html.com/rss2html.php on line 357

    Last Updated: 12/31/1969 07:00 PM

    This page was created using RSS courtesy of FeedForAll


    What is striking about the result is that both platforms have generally provided superior service, timely responses. Yet, these errors are not listed on either google or Technorati suggesting this is a new error related to something recently changed on 2RSS.

    There could be a validation issue, which would raise the question with Newsgator: Is it possible the auto-generate tool is generate a feed that appears to be valid, but is actually not?

    Actually, the problem appears to be related to the Newsgator permissions. If we validate feed, it doesn't work suggesting that the Newsgator URL for this particular URL-watch is only intended to be maintained on the Newsgator Online site.

    In other words, at this point it appears as though there really isn't a problem:

  • Newsgator Online correctly reports content along this URL

  • 2RSS correctly reports the status of that content

  • Newsgator Online adequately prevents content on a private URI to be released


    LEGAL NOTICE


    Creative Commons License

    This work is licensed under a Creative Commons License.

    You may not copy any of this work to promote a commercial product on any site or medium in the universe.

    If you see this work posted on a commercial site, it violates the creative commons license; and the author does not endorse the commercial product.

    Free to use for non-commercial uses. Link to this original blogspot and cite as .


    The only way to view this URI appears to be if Newsgator Online were to adjust their settings allowing a private feed to be converted to something else. How Newsgator Online, or any aggregator for that matter, would be able to both maintain a private feed, yet allow that feed to be adjust by an external site remains to be understood.

    Perhaps there is a way. Anyone have any ideas?


    XML Osmosis

    Private feeds interacting with public forums


    Yes: Create a flexible firewall. One that is like an two-way reverse osmosis used for desalizating water.

    Although the feed may be protected, it still can pass through the membrane to interact with something else, all the while it still is protected.

    The trick would be to apply the lessons from osmosis in biology to the aggregators and the external platforms.


    XML Reverse Osmosis Modules


    The modules would be:

  • allow the firewall to exist;

  • break down the URI into a transportable code along the firewall;

  • reconstruct it at the external platform;

  • have it interact with the external platform;

  • capture the result in an external cache;

  • breakdown the newly created feed into something that can cross the barrier;

  • then recombined back into a valid feed or data that the originating platform would recognize as valid;

  • then re-accomplish the results to send back the confirming message back to the external platform that the URI was in fact, valid [even though it was protected].


  • The trick to make this work would be to have a method to integrate with an external platform in a way that accepted the URL-pseudo-code [after being broken down] in way that protected the code from outside review, but at the same time ensured the code was workable.

    How to make a code that can breakdown, interact, recombine, but still not be readable?

    If we go to our 1/2-code principle used in creating a two-way search engine, it would be possible to:

  • export only part of the original code;

  • let the external tool work on that portion, then

  • recombine the result with the other half.

    If another platform attempted to use the ejected code, it would never work because they didn't have the matching key, which only Newsgator would have.

    Presto! The private feed can now interact with a public platform, but still be private.
    " />