Network effects and RPC

[Mark Baker]

> But, I can posit an entirely new frame of reference for the problem of
> search engine notification specifically: proxy chaining.
> 
> In this view, consider a webDAV PUT from mydesktop to mysite. It can be
> safely proxied; so what if mysite further relayed the same damn PUT to
> google?
> 
> In other words, what if the $29.95/mo contract was that "Google promises to
> be a proxy depository for mysite -- and one of the side effects shall be a
> full-text index" (or even substitute Akamai and the side-effect of mirroring
> your site worldwide).

Interesting.

> Thus, google.com SUBSCRIBEs to all PUT transactions agains urls anchored at
> mysite.com. It's just that rather than proxy chaining THROUGH google, it's
> attached at the END of the proxy chain.

So how does one automate subscriptions to a class of HTTP transactions?
I'm thinking "GET /transactions/http/method/put". 8-)

> So what would you guys think of the "simpler" solution to replaying HTTP
> traffic against multiple sites? Somehow I fear that the
> implementation/adoption costs are higher even though active-proxies are
> conceptually simpler.

What's required to implement this?  A surrogate router installed at mysite
providing the subscription interface to Google.  The hard part would be
integrating the router with the DAV server; no standard interfaces.

Adoption would also be aided by a wide variety of third party services
willing to help out mysite.  But then you're into Chicken v. Egg.
What's a router vendor to do?

MB