----- Original Message -----
From: "Vincent Massol" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 21, 2001 10:25 AM
Subject: Re: Cactus Roadmap & V2 Propsal RFC
[snip]
> >
> > As stated above, ideally mock objects would work as another container.
> > So, no need to choose beforehand.
>
> Well, that's the goal but the question is : how do you implement it to be
> transparent ?
> The real challenge is that the architecture is different with IC and MO.
For
> IC there is an HTTP connection made and there is a proxy on the server
side
> ... Hey, wait a bit, I suddenly have an idea ...
>
> Why not implement a mock (or rather a simple) HTTP server (or simpler yet,
a
> mock HttpURLConnection that would be used when doing MO tests). The goal
is
> to have the same architecture for both MO and IC and then the "client"
part
> of Cactus would stay the same and on the "server" side there will be a
> factory that will return either real container objects or MO ones ... Yes,
> good idea Alex .... :-)
>
I thought I had had a good idea ... but after thinking a bit more about it,
I really don't know what good it would do as anyway we need to have a
different client part for IC or MO. It is just complicating things ... :)
The architecture would rather be, I think, like this :
Cactus Test Case ------> Cactus CLI ------> IC ----- HTTP -----> IC Proxy
Cactus Test Case ------> Cactus CLI ------> MO
Cactus Test Case ------> Cactus CLI ------> PF ----- HTTP -----> Real server
Thanks.
-Vincent
