On 10/2/03 17:37, "Vadim Gritsenko" <[EMAIL PROTECTED]> wrote:
>
> How about webservices (ws?) block? We have axis stuff in the scratchpad
> which also could be thrown into it.
Well, I don't know... But, I _do_not_like_ web services... :-)
I need, though, an HttpProxyGenerator: in my application, I basically have a
Cocoon instance which (behind some tons of firewalls), deals with databases
and search engines... All this data is then "presented" in XML (mainly RSS
and some proprietary doctypes) to a "front-end" rendering-only cocoon
instance, caching the backend when needed, and presenting the requested
content to the client (we are going to have several of those)...
Basically:
+--------+ JDBC
| Oracle | ------+
+--------+ | +------------------+
+---> | "Backend" Cocoon |
+--------+ | +------------------+
| Lucene | ------+ |
+--------+ FILES | XML over HTTP (RSS + Proprietary)
|
+--------------------+--------------------+
| | |
V V V
+------------------+ +------------------+ +------------------+
| Rendering Cocoon | | Rendering Cocoon | | Rendering Cocoon |
+------------------+ +------------------+ +------------------+
| | |
| HTML | WAP | Feed (proprietary)
| | |
V V V
+--------+ +--------+ +--------+
| Client | | Client | | Client |
+--------+ +--------+ +--------+
In other words, the "Backend" instance deals with the databases and our
search indexes, caching the data (for example an article) locally. When one
of the front-ends requires an article, I don't have to think about
replicating the same database-magic in the front-end, I simply say that my
article resides on the backend, and I use the HTTP Proxy to get it.
So, literally, for me an article is that XML document found at
http://backend/article?id=xyz
This is what concerns _me_. The graphics team have their all set of stuff in
the front-end that they can deal with (and which I don't really care about).
They only know that the article is at that given URL...
But that's far from writing anything even _close_ to some WSDL markup! :-)
IMO, the problem of accessing XML remotely over an HTTP connection is quite
different from doing the whole "web-services" thing... They should be two
separate blocks, IMVVVVHO...
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
