On 06/22/10 02:09 PM, Dave Miner wrote:
On 06/22/10 12:13 PM, Sarah Jelinek wrote:
Hi William,
On 06/18/10 07:57 AM, William Schumann wrote:
Sarah,
On 06/17/10 04:41 PM, Sarah Jelinek wrote:
Advantages:
- documents are valid and can be parsed and validated individually
without manipulation
- useless tags ai_criteria_manifest, ai_embedded_manifest,
sc_embedded_manifest and their closing tags disappear
Disadvantages:
- AI web server must dynamically merge the documents for the
default case (mitigated by the small size of the documents)
Why does it have to merge these? We apply the SC manifest in it's
entirety to the client for use by SMF, right? So, merging them for
transmission and then separating them on the client seems like work
we don't need to do.
Well, presently the SC manifest is embedded into the AI manifest.
Although they both contain system configuration information, they
are of two different incompatible formats. It makes some sense to
send them with one HTTP GET to reduce the number of network
transactions - I just think it's simpler to merge them in a standard
format like MIME, then separate them on the client.
We may presently do this, but I think that even if we allow for
specifying the location of the SC manifest remotely we can validate
it on the client. Or, if the user provides a validation method we can
use that as well at manifest parse time. A user can also validate it
independently using xmllint. I realize that the user could change it
in between validation and the use of it, rendering it invalid, but we
error out on the client if that happens.
OK, that addresses any desired validation.
With the new schema definition I don't propose merging it. It will be
using a DTD as will the AI manifest so it isn't different any more.
How do you deliver more an AI manifest with multiple SC manifests?
How would the protocol work, RE: HTTP GET requests?
So, after chatting on the phone it became clear to me I was
misunderstanding the term "merge" in this context. Using the MIME
multipart document to transport the AI manifest and multiple SC
manifests will work. The AI client just has to parse out the SC
manifests and apply them to the alt root as required.
I'd much prefer that we not invent additional encapsulation
mechanisms. We already have the wanbootfs; that would seem to be a
much simpler way to deliver a set of configuration manifests than
doing MIME encode and decode.
ok, fair enough. I am good with using wanbootfs for this.
sarah
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
