Lists Home |
Date Index |
- From: Joel Riedesel <email@example.com>
- To: David LeBlanc <firstname.lastname@example.org>
- Date: Mon, 18 Jan 1999 20:02:36 -0700
Are you referring to the Coins work? (That might be a bit
more than what you're thinking of as that's more like serialization
of Java objects into XML - if I recall correctly.)
This would actually be quite easy to do right now.
In the server environment that I work in, we have our web server
embedded in our Java server environment. That enables us to
deploy our server with servlets without requiring non-technical
people to figure out servlets, web servers, etc.
We could continue down that road and use HTTP and XML for all
of our communication quite easily at this point. However, for
some other reasons I'm not ready to go to that step (almost
entirely performance related... our architecture has plug in
processing code that needs to operate very fast...).
(However, to back-peddle just a little, we'll probably offer
multiple APIs for some of our architecture, that allows just this
But, the point being that this is doable today (in my opinion) and
without a lot of effort. Throwing XSL into the mix, and now you've
really got an open modular system for the Web.
David LeBlanc wrote:
> Darned if I can remember where, but I think I surfed past someone doing such.
> Maybe it could be called Xorba? :-)
> Dave LeBlanc
> At 06:09 PM 1/18/99 -0800, Rob Schoening wrote:
> >Personally, I think that there is some real opportunity for innovation here.
> >If there was an XML-based spec for serialization and invocation, I think
> >that it might be possible to implement an IIOP-ish protocol using XML. This
> >would be really interesting, IMHO, since it would allow the document and
> >component models to converge. CORBA, EJB, and DCOM tend to be rather
> >heavyweight ($$$) in deployment. But if the client could be pared down so
> >as to require little or no client-side code for certain transactional
> >systems, things could get really interesting. For straightforward
> >deployments, XML over HTTP (or even SMTP) could have compelling value.
Jnana Technologies Corporation
303 805 8275
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)