Re: Ancient history

Paul Rubin <http://phr.cx@NOSPAM.invalid> writes:
> A browser does much more than render HTML. It has a fancy GUI instead
> of a crude command line interface; it gets and processes data from
> multiple network sources in parallel; it renders images; it interprets
> javascript, and it sprouts improvements all the time in response to
> technical developments and user requests. Yes, you could maybe do a
> more careful job writing something minimal and strictly
> standard-conformant; but we're talking about full-featured, responsive
> browsers of the type that actual users want to actually use.

when we were doing this stuff for the original payment gateway with
this small client/server company that wanted to do payment
transactions on their server ... we could specify some amount of the
integrity and security implementation & operational requirements.
http://www.garlic.com/~lynn/aadsm5.htm#asrn2
http://www.garlic.com/~lynn/aadsm5.htm#asrn3

i've more recently done some postings in some SOA threads that it
might be considered one of the first web SOA implementations.
http://www.garlic.com/~lynn/2005i.html#42 Development as Configuration
http://www.garlic.com/~lynn/2005i.html#43 Development as Configuration
http://www.garlic.com/~lynn/2005i.html#44 SqlServerCE and SOA - an architecture question

however, we had no approval/veto authority about what went on in the
client implementation and much of the client/server interactions ...
primarily just limited to the server and the payment gateway
interactions (although i did give some presentations on business
critical dataprocessing requirements for network implementation that
had some number of the client implementors present).

-- 
Anne & Lynn Wheeler | http://www.garlic.com/~lynn/