Reply to thread

Message: [QUOTE="Andy Dingley, post: 3032133"] Apart from the XML parsing details, you should be very careful with that as a technique. I just wouldn't do it, at that simple level. You need to add some level of caching for "production" code. If it works, then it's a slow page - your server-side code has to go off and retrieve something external every time. If it works, then it hammers the remote server. They might object to this, they could well ban or throttle your access (even to a "public" RSS feed). It often won't work. If the remote server is down or just slow, your page will appear to have failed too. What you're building here is an "aggregator" (you can search for that term), and quite possibly close to an RSS aggregator. Most of those separate the loading and serving of remote feeds, and cache via a database in the meantime. This provides a better local service, it limits the remote load, and it also provides some robustness when the remote service goes down. I'd also question whether it's a good idea to have "Menu XML" in this way, or if you'd be better fitting it into the overall RSS framework, possibly as an RSS 1.0 Module. A simpler way would be to use "Menu XML", but just to embed this within Atom (or RSS 2.0) to handle the syndication aspects. [/QUOTE]