RE: routing requests to two different servers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: solprovider@xxxxxxxxx [mailto:solprovider@xxxxxxxxx] On 
> 
> Splitting a stream is useful.  Older people remember when forms were
> sent in triplicate.  Then office workers made a copy of every paper to
> cross their desks.  Now smart people keep a copy of every file passed
> to others.
> 
> Splitting a stream is not unusual.  Unix has the "tee" command.
> Apache Cocoon has the TeeTransformer.  Apache httpd copies part of
> each request into the log before fulfilling the request.
> 
> Splitting a stream is easy:
> while(b = in.read()){  out1.write(b); out2.write(b); }

The *concept* isn't unusual - what's complicated is applying the concept
to *HTTP*. I think, rather than having to write a web-server, the OP was
hoping it could be done using config directives - maybe something like:

ProxyPassSplitStream / http://server1
ProxyPassSplitStream / http://server2

Rgds,
Owen Boyle
Disclaimer: Any disclaimer attached to this message may be ignored.  

> 
> Discarding the output from the test server is difficult, but not
> impossible.  When configuring the server for the above code:
>    Connection1 = client<-->splitter
>    Connection2 = splitter<-->production server
>    Connection3 = splitter<-->test server
> The splitter should compare responses from the production and test
> servers and log the differences.
> 
> I am uncertain this functionality should be added to Apache httpd.  I
> recommend writing a simple fast dedicated server to handle splitting,
> logging, and comparing.  That server could be added and removed from
> the production stream without affecting the other servers beyond an IP
> address configuration change.
> 
> solprovider
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP 
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>    "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
 
 
This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux