I use the Sentillion components and they could be switched out to another component with the same interface, but that would be like anything else. If you take RPC Broker, made something that looked just like it but spoke over XML and Web Services - then yes, you can swap it out.
On the server/client communication for CCOW, it is HTTP-like traffic but I'm not sure what's "swappable". The Sentillion pieces have a very good architecture for support (in terms of accessing client CCOW Managers, logs, status, etc) and I'm not sure if this is part of the "standard". Being "standard compliant" doesn't mean you can't add on. As such, it may make more sense to think about implementing a client and server component that works together rather than replace any one piece of a given solution. Does anyone else know of other CCOW enabling frameworks? /David. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of steven mcphelan Sent: Tuesday, December 28, 2004 9:42 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] HealtheVet Desktop Components If anyone wants to implement CCOW as David and Cameron has stated, you have to have two components. One is applications which are CCOW enabled. If an application is compliant with CCOW standards, then that application should be able to run whether or not a context manager is online or not. The second component is a CCOW content manager. As Cameron stated, the VA chose to implement Sentillion's content manager which is proprietary. However, if any application is CCOW compliant, they should work with any CCOW manager. I am not 100% certain about that last statement. Even though an application is CCOW complaint, I do not know the CCOW standards well enough to know if one's application is 100% CCOW standard compliant, will that application work with any CCOW content manager with no modification required? But even if modification is required, it should be rather simple to modify since I would assume that the CCOW code would be encapsulated and thus easily modified to work with any CCOW manager. The CCOW manager by itself is not dependent upon any specific patient database. The applications submit the content requests to the CCOW manager for that manager to maintain and coordinate with any other applications you may be running that are CCOW compliant. ----- Original Message ----- From: "Nancy E. Anthracite" <[EMAIL PROTECTED]> To: <hardhats-members@lists.sourceforge.net> Sent: Tuesday, December 28, 2004 6:18 AM Subject: Re: [Hardhats-members] HealtheVet Desktop Components > No, Nancy hasn't done it and I strongly doubt Nancy will have the foggiest > idea how to help if she did try it. Remember, Nancy was the one who asked > what CCOW is. ;-) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
