Confusion about Full Text Search in SSDS

re: Confusion about Full Text Search in SSDS

mamund — Sun, 22 Jun 2008 20:06:39 GMT

Hey, it's fully understandable that you have 'back-end' and 'front-end' rollouts that might be 'out-of-sync' from the user perspective. But *please* keep us posted on both aspects, OK?

Knowing that an item is in the back-end, even if it means we'll need to wait a bit before it's exposed to clients, is still intersting news.

re: Confusion about Full Text Search in SSDS

rogerj — Sun, 22 Jun 2008 21:22:19 GMT

Mike,

I agree wholeheartedly.

Cheers,

--rj

re: Confusion about Full Text Search in SSDS

Soumitra Sengupta — Sun, 22 Jun 2008 21:47:34 GMT

Thanks Mike and Roger. There are 4 classes of feature work we do:

a. Features exposed through the FE webservice. The ETag support Jeff talks about is one of them. There are 2 flavors of this - one through our REST head and other through the SOAP head

b. Feature work we do in the BE (eg. the FT index replication work we just did)

c. Feature work that enables us to operate the service efficiently. These we call service delivery related work. Quota enforcement, throttling, tracing, logging etc. would fall in that bucket.

d. Feature work to improve performance, reliability, scalability, geo-replication etc.

Then there are feature work which we will do as we integrate with other services from Microsoft as they come online. You will hear more about these as time goes by.

I will call these out as we go. Again thanks for your comments. Appreciate it.