RE: Developments in the review cycle

Subject: RE: Developments in the review cycle
From: Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 12 Apr 2016 07:54:11 +0000 (UTC)

Erika says==============But with all this virtualization trend going on, I guess boxes will gradually be replaced by networking SW run on regular servers and then we can apply Mark?s theory.==============
Actually, this is where I don't see Mark's theory working. Virtualization translates into distributed applications (microservices) -- multiple "server" components that make up the final "application". The thing is, your "application" might be different from mine, and we may never know which components a specific user will use or have access to in advance of the user signing onto a session. When that happens, you can't know what docs to deliver. A single, centralized doc server can't scale to the possible combinations. The answer is to distribute the docs with each component, and provide a client that aggregates the content at request time. This is what I'm doing at VMTurbo (a virtualization platform company).

Also, there are still security constraints. The obvious -- when an enterprise doesn't allow external access -- demands that the components be installed behind the firewall, and that's where the docs should live as well. But there's another aspect -- dynamic content. With a client that dynamically aggregates content at request time the content can come from anywhere, including the component data model itself. That means the docs can build content that reflects the user's state, on the fly. To do this, if the user's data is behind the firewall, then the docs must also be behind the firewall -- or at least the doc client must be.Â

We have to move away from the notion of a centralized doc server. That's just another silo. There are two directions to go here. Either find the UNIVERSAL SILO -- The one silo that can do everything you need today and tomorrow -- or implement a system that connects silos. IMO, the latter is the more likely, more flexible, and more future-proof.
Visit TechWhirl for the latest on content technology, content strategy and content development |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Previous by Author: Re: Developments in the review cycle
Next by Author: Re: Alternatives to MadCap Flare
Previous by Thread: Re: Developments in the review cycle
Next by Thread: Working Off Site

What this post helpful? Share it with friends and colleagues:

Sponsored Ads