tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/381-xml-feed-sizeCascade CMS: Discussion 2015-08-27T20:28:04Ztag:help-archives.hannonhill.com,2010-02-09:Comment/99936462011-09-16T22:41:44Z2011-09-16T22:41:44ZXML feed size<div><p>Interesting ideas Matt.</p>
<p>We satisfy a similar need by synchronizing these courses as page
assets into Cascade via Web Services. This has some advantages,
notably that it allows us to deploy a hierarchical master website
that allows people to browse all courses in several terms across
several schools and departments in one place. We publish a sort of
JSON-file database to the web server that a frontend desktop web
site reads at each folder level as necessary when the user is
browsing. The courses are synchronized into folders, like
4440/WCAS/ANTHRO/111-5/11123 which is term number, school code,
department code, course number, and finally a sort of unique course
number (it's really just a section of the course but the asset name
is not the section number). In addition to the web site, each of
these folder levels and courses has a configuration that publishes
a mobile friendly view for browsing that way.</p>
<p>We haven't pulled in many huge XML documents via Feed blocks but
I can't imagine it would work super well. One issue with Feed
blocks is that if for some reason reading the file fails due to a
busy or overloaded web server or a strange character encoding error
in the XML file your publish job will continue to run with errors.
In the first case, it will probably display nothing on the page(s)
and in the second it will at least likely generate an error in
either the publish report or the Cascade system log and not publish
anything. With the approach we chose above it was really painful to
synchronize these assets into Cascade up front (i.e. keeping
special characters and things like that out during asset creation)
but at least we knew there wouldn't be a problem when rendering
pages based on the data. Also, if there IS a problem with just one
course, it is basically isolated publishing pages about that single
course (and the publish report does give us notice that there was a
bad character or some malformed HTML in one of the strings).</p>
<p>From a performance perspective In the end I suppose you could
generate a fake file of about that size and do some tests on
it.</p></div>Lee Roberson (Function Digital LLC)tag:help-archives.hannonhill.com,2010-02-09:Comment/99936462011-09-30T17:18:40Z2011-09-30T17:18:40ZXML feed size<div><p>I've been interested in using this technique as well - using a
feed block to pull in a non-feed XML file, since it's potentially
such an easy approach to get external XML into the system. Based on
limited testing, it seems to work well, but I'm not sure if future
releases might suddenly require/validate against specific feed
formats (RSS/Atom) and therefore reject other XML sources.</p></div>eportertag:help-archives.hannonhill.com,2010-02-09:Comment/99936462012-06-21T17:13:49Z2012-06-21T17:13:49ZXML feed size<div><p>Hi Matt,</p>
<p>I was going through some older discussions and saw that this one
was still open.</p>
<p>Were you able to get your class schedule implementation working?
If you did, would you be willing to share for others to have a look
at what your institution did?</p>
<p>Thanks!</p></div>Ryan Griffith