On Thu, 20 Mar 2008 09:07:08 -0700 (PDT)
Raghav Kapoor <[EMAIL PROTECTED]> wrote:
[...]
> > Any particular reason why need the server in this
> > situation? pretty much
> > everything you are doing can be done locally.
> > Except, probably, cross linking
> > between client's documents. I have no idea in what
> > kind of environment this app
> > is supposed to run (home? office LAN? the interweb
> > :P ? ).
>
> So its going to be a client/server app where all the
> documents will be stored on the client and only
> metadata of those docs will be sent to the server.
> That way server does not have to store any real
> documents. Its an internet based application. Search
> on the server will read the metadata for keywords and
> send the request to all the clients that contain
> documents with that keyword. We cannot store
> everything on one client, all clients are different
> machines distributed all over the world.
I see.
> > you don't need a webserver for this, just generate a
> > page in from your
> > webserver with file:// links and all you need is to
> > render it locally.
>
> How will the client serve the documents stored locally
> through a standard mechanism (like port 80) to send
> documents to the server when the server requests the
> documents ? The client will not open any special ports
> for the server, so we need the web server, I guess ?
I see. Sure, webserver will work for this....but tcp/80 will also have to be
opened @ the client's firewalls. IOW, whichever way you chose for the server to
connect each of the clients needs to work across a global namespace and across
firewalls...
contact me privately if you want to discuss more on this ... it hardly relates
to Solr per-se.
[.....]
B
_________________________
{Beto|Norberto|Numard} Meijome
Percusive Maintenance - The art of tuning or repairing equipment by hitting it.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
