Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Message-ID: <4B0D7B07.40400@ice-sa.com>
Date: Wed, 25 Nov 2009 19:44:23 +0100
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: users@httpd.apache.org
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: users@httpd.apache.org
References: <bbf56fae0911250609r5b9725ecr96fd986053f709ab@mail.gmail.com>
	 <2e027be00911250611w1bc70785t2cb457f741761b4a@mail.gmail.com>
	 <bbf56fae0911250619w503df242ra6d45fb4840e41e7@mail.gmail.com>
	 <4B0D4A5C.6010405@ice-sa.com>
 <bbf56fae0911250850x16966a1wedd29b9fce4ba607@mail.gmail.com>
In-Reply-To: <bbf56fae0911250850x16966a1wedd29b9fce4ba607@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] Apache httpd replication / proxy mirror server?

nino martinez wael wrote:
> It's a bit complicated. So I'll try to explain it in a simple way.
> 
> The user are calling(via phone) an IVR application which in turns interprets
> vxml. The vxml page then has an option to record and save the recording.
> When the vxml page saves the recording it saves towards tomcat which then
> places the file in a repository which then are served by Apache httpd, we
> have more apache http servers for failover and it's here the need for
> replication comes.
> 
> All this we can code our way out of, but if there's something already that
> does this it would be nice with some recycling. I was thinking that the
> Apache http server that got the new file could push it to the others.
> 
Allright. I have no idea what IVR is and no wish to look up another 
acronym, but I think I get the idea.
So, the answer is still no, there isn't a standard Apache module that 
will do that kind of synchronisation.  Specially since the way you 
explain it, Apache itself has no idea that this file has been loaded in 
the first place, nor where.
So it is either taking care of it at the level of your own code, or use 
rsync as someone else suggested earlier (and which is probably the best 
idea overall).
rsync also works under Windows, we use it.
And if you have trouble setting it up, nowadays setting up a Linux box 
is really not difficult.  You could set up one just to do that, which 
would take care of synchronising between all your servers.  It is very 
efficient, as it will only copy whatever changes, even within files.

As for the ideas I was referring to earlier, it would have been 
different if the files were uploaded via DAV for example, because then 
Apache /would/ know.

---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org