|
Posted by ilya on June 12, 2006, 9:04 pm
Please log in for more thread options
I won't attempt to answer the Indexing service vs MSN Desktop Search, but as
for using WDS on a server, you can most certainly do that. WDS also supports
advanced search (boolean restrictions on properties or locations, for
example), and you can intercept results from the query and do with them what
you need to prior to returning them to your users. Search SDK comes w/ a
.NET wrapper for the API that lets you do all that from VS.NET.
a better question might be, though, whether you *should* do that. i doubt
WDS was designed (please correct me here, someone, if i'm wrong) for
hundreds (or tens?) of users searching for stuff all at the same time, so i
don't know what kind of performance issues you're going to run into. of
course, if this is a small company with not a lot of searching going on,
then maybe you'll be OK. I'm not saying that you won't be w/ lots of users,
i just haven't seen any kind of performance tests done in such a scenario -
nor is it clear to me if it's supported (officially).
hth
ilya
> Hi,
>
> Can someone tell me what the distinction is between Microsoft Indexing
> Service and MSN Search? Does MSN Search use Indexing Service as its
> underlying search engine?
>
> I want to create a search tool inside a corporate intranet (in ASP.NET
> 2.0)
> that searches in files on the File Server and displays a list of results
> on
> the web form. I know I can use the MS Indexing Service API directly, but
> I
> think MSN Search is faster and offers better indexing, am I right? Can
> MSN
> Search even be installed on a server (running Windows Server 2003)?
>
> Thanks!
>
> Aaron
| 
XML Sitemap