RE: [Podserver-devel] Does anyone have a database with the schema (and or any PHP code to pull the details from it) yet?

[Tom K. <li...@te...>]

As far as the Remote PodServer idea....
The hope was that it would be simpler to just update remote files than =
to do
database replication or clustering.  Heck, if we wanted it could be a =
simple
application that just parsed the RSS feed (this would have to happen =
before
general release to the public) and grab the files it needs from there.  =
If
we can keep all the junk (feeds, users, keywords, show notes, etc) off =
the
remote systems and just have them deal with the files, I think we'll =
save
ourselves some trouble.

I've never done database replication or clustering, but I've heard that =
its
very difficult to setup and maintain.  Does MySQL replication require =
either
server to go offline?

Tom

-----Original Message-----
From: pod...@li...
[mailto:pod...@li...] On Behalf Of =
Foster,
Richard - PAL
Sent: Friday, January 13, 2006 11:15 AM
To: Tom Kent; pod...@li...
Subject: RE: [Podserver-devel] Does anyone have a database with the =
schema
(and or any PHP code to pull the details from it) yet?

Tom,

I agree that there should be no need for a manual FTP operation. It was
certainly never my expectation that there should be. Uploading the file
could (relatively) easily be accomplished from the same web page as the
entry of the feed-related information. The original file name, and the
name used after uploading may not (and probably wouldn't) be the same.

Yes, if the files are available as "plain mp3" files out on a server (or
server cluster), there is no requirement for your second script. (That's
another reason for considering it, since it would mean less "code" to
maintain). It would not break the "central reference" concept since
information about the location of all the files would still need to be
in the database so the RSS feeds could be generated. It does have the
downside that if the files are moved manually (as opposed to through any
script we provide) then the references would end up broken.

Why reinvent the wheel with the "Remote Podserver"? MySQL (at least) can
handle having copies of the database in multiple locations natively
through database replication. (Note: I have not investigated if partial
replication is possible, or if it is only possible to generate a full
replica. I would be surprised if partial replication is not possible).
Similarly there are already well designed and widely available
clustering solutions for web servers. I have not investigated them, but
I believe it should even be possible for listeners to "donate" server
space effectively acting as a full or partial mirror of the primary
site. Fr Roderick's server would effectively act as a manager,
redirecting listeners to the appropriate mirror locations.

Regards,
Richard


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dick
_______________________________________________
Podserver-devel mailing list
Pod...@li...
https://lists.sourceforge.net/lists/listinfo/podserver-devel