Eddie Epstein wrote: > On 10/18/07, Thilo Goetz <[EMAIL PROTECTED]> wrote: >> >>> merging for parallel processing steps, and will be used to implement a >>> delta-CAS transport model that only sends out to services the data they >>> require and only sends back new and modified data. The same design used >> for >>> delta CAS will allow us to give users details on CAS changes for every >>> processing step, when desired for debugging, with little or essentially >> no >>> extra overhead. These requirements may be easily handled in a new CAS >>> design, but we should take them into account in the redesign process, >> not >>> after an implementation. >> Maybe these requirements should be discussed here first >> before we assume they will be implemented? >> >> > Perhaps "requirements" was the wrong word here; "opportunities for > improvement" would be better. The envisioned implementations have no > dramatic impact on existing design. But as long as we are discussing, any > comments? > > Eddie >
If by "existing design" you don't mean CAS internal implementation details, that's fine with me. I'm personally not very interested in sending XML serializations of the CAS around the network. If what you're proposing affects my ability to change the CAS implementation, then I will have some comments. --Thilo
