Re: Beagle and NFS

[Joe Shaw <joeshaw novell com>]

Hi,

On Tue, 2006-02-21 at 16:57 -0500, D Bera wrote:
> (Thinking out loud) What happens if the unix socket in beagle is
> replaced by tcp socket ? I dont remember the code, but it doesnt look
> like beagle is using some special feature of unix socket which is not
> present in tcp sockets.

Right, that's what I was thinking for a first pass.  It should work
transparently.

> That would only solve a part of the problem. There still needs to be
> work done on authentication/access control/remapping of uri (e.g.
> remote:// or fish:// or ssh:// ...)/mechanism to *open* results (e.g.
> using sshfs or smbfs etc.). and many more.

Right, which is why using a plain TCP socket probably isn't the way to
go here.  HTTP has authentication mechanisms that could be used, but it
isn't great for sending live notifications.

I think the web services system just serves the results up over HTTP; we
could do something similar with a new system.

> Just a side note, networked beagle implementation was done separately
> (by Fredrik, IIRC) and later absorbed by beagle webservices. beagle
> webservices implementation is complicated due to the lack of any
> httplistener in mono (at that time). Recent mono versions have an
> embedded httplistener, so the code can be simplfied and made to work.

Yes, possibly.  The current web services backend should at least be
considered in any efforts to improve networked searches.  But I don't
think doing a full blown SOAP-based web service is the right thing to do
here; we just don't need that kind of complexity.

Joe