Hi, 

 I am planning to provide web access to a text search engine using web 
forms and possibly web services. I have few questions. Could some of you 
help me solve these issues.... 

My backend search engine object is quite large, so I prefer to keep it as 
a static object, which will be started when the server is turned on and 
survive during and after  the "server round trips by the users". 

Within the "Page" object I should be able to redirect the requests to this 
static object and recieve "search results" 

My questions are: 

1. what is the best way to implement this? currently I am thinking about 
three layers: a web form(presentation), a data view object, the static 
back end object. 

2.should I implement the static back end object as a windows service? 

3. if I am going to get rid of the data view object , how can I refer to 
the static object within the "Page" object. 

Thanks in advance 

sujeewa 

Static object really crappy solution... Even in ASP.NET.. Also it's 
pointelss to host it usin' Web Services...
Well how would I do it....

0 level: Database with Stored Procedures
1 level Web Services (try SQL XML it's the best)
2 level Presentations by applying XSL to returned from Web Service XML.
3. Pint of Guiness (if it's friday).

Cheers.



>From: "SUJEEWA ALWIS" <sujeewaalwis@a...>
>Reply-To: "aspx_beginners" <aspx_beginners@p...>
>To: "aspx_beginners" <aspx_beginners@p...>
>Subject: [aspx_beginners] web search engine design
>Date: Tue, 16 Apr 2002 18:15:04
>
>Hi,
>
>  I am planning to provide web access to a text search engine using web
>forms and possibly web services. I have few questions. Could some of you
>help me solve these issues....
>
>My backend search engine object is quite large, so I prefer to keep it as
>a static object, which will be started when the server is turned on and
>survive during and after  the "server round trips by the users".
>
>Within the "Page" object I should be able to redirect the requests to this
>static object and recieve "search results"
>
>My questions are:
>
>1. what is the best way to implement this? currently I am thinking about
>three layers: a web form(presentation), a data view object, the static
>back end object.
>
>2.should I implement the static back end object as a windows service?
>
>3. if I am going to get rid of the data view object , how can I refer to
>the static object within the "Page" object.
>
>Thanks in advance
>
>sujeewa
>


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

--part1_9.2692700f.29edf61c_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit


hi Dimitry
 
 Thanks very much for the suggestion- one problem though, the search engine 
back end is not a conventional database server, it is an associative neural 
network and once trained with large amount of data it can be fairly big, so 
it is not feasible to keep multiple copies inside the memory.....any 
suggestion will be a big help


sujeewa



In a message dated 16/04/2002 20:10:37 GMT Daylight Time, brook74@h... 
writes:


> Static object really crappy solution... Even in ASP.NET.. Also it's 
> pointelss to host it usin' Web Services...
> Well how would I do it....
> 
> 0 level: Database with Stored Procedures
> 1 level Web Services (try SQL XML it's the best)
> 2 level Presentations by applying XSL to returned from Web Service XML.
> 3. Pint of Guiness (if it's friday).
> 
>