Dynamically Updating URI’s
Overview;Blogging these days tends to be a link-heavy affair. Some blogs/people/posts may link to up to 15+ URI’s in one single article. We all understand that URI’s are not meant to change, their Server/Host/Publishing Platforms/Directory Structure is meant to be static. Reality, however, occasionally paints a different picture. Servers, Hosts, Publishing Platforms, and Directory Structures do change. The reader gets a lot of 404s, the indexers/crawlers see the site as out, and the author’s original work goes to waste.
Premise;If I link to something, I don’t care where it is, I only want it’s content, something that will probably remain somewhere on the internet, just different to where it was before. Using this as the base concept, and mechanisms TrackBack/Pings, we can create a form of Dynamically Updating URI.
Method;When an article is written with links, it pings the link’s blog; the result of which shows up as a track back on the linked to blog.
What I believe should happen at this point is that both the linker and the linked should create a sessions, with one-time MD5 Authentication. The total of the session should contain LinkerBlogURI, LinkedBlogURI, and the one-time MD5 Authentication Key.
Example;If the Linked Blog URI updates, it should Ping the Linker Blog stating “LinkedBlogURI updated, Update LinkedBlogURI to new resource location. Authentication Key attached.”
Thoughts?
No Comments Yet