Would anyone be interested if i extended this into an
XML file?

I'd like to eventually extend this so it describes the
server and possibly the data on it as well as
replica's of that server (for load balancing/failover)

and any other options that may be nifty.

Something like

<?xml version="1.0" encoding="ISO8859-1" ?>
<SERVER>
  <QUERY>
     <NAME>search1</NAME>
     <HOST>search1.nutch.org</HOST>
     <PORT>9999</PORT>
     <DESC>Some Description</DESC>
  </QUERY>
  <QUERY>
     <NAME>search2</NAME>
     <HOST>search2.nutch.org</HOST>
     <PORT>9999</PORT>
     <DESC>Some Description</DESC>
  </QUERY>
  <DB>
     <NAME>db01</NAME>
     <HOST>db01.nutch.org</HOST>
     <DESC>Db server description</DESC>
  </DB>
</SERVER>


The concept i'm trying to think of is a file that will
eventually describe the purpose of each server in your
"cluster" and be able to extend nutch to define
directions.

Espcecially as we move towards distributed webdb and
such. It would be nice to just descrbe the servers in
a map in such a file.

I'm working on a web management "console" of sorts and
i am leaning towards mapping out the environment and
optimizing query/search over distributed db as well as
distributed fetching to better manage a huge system
and just thinking of baby steps we could do to move to
such an interface.


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers

Reply via email to