=-= [摘要] -=- Google Street View's photo data could be used for more than just plain showing it to users. Internally, Google could do some image analysis -- like OCR, optical character recognition, to convert text contained in the images of the houses, shops and so on to text. Such text could be utilized for several things: Google could be able to make the streets searchable through a
Adenauer schrieb: On Tue, 08 Apr 2008 15:47:28 +0200, Werner Schneider <hvymetal@gmx.com> wrote: Adenauer schrieb: On Tue, 11 Mar 2008 21:37:45 +0100, Werner Schneider <hvymetal@gmx.com> wrote: Adenauer schrieb: On Sun, 17 Feb 2008 17:23:20 +0100, Werner Schneider <hvymetal@gmx.com> wrote: Adenauer schrieb: On Tue, 12 Feb 2008 17:56:48 +0100
Adenauer schrieb: On Tue, 11 Mar 2008 21:37:45 +0100, Werner Schneider <hvymetal@gmx.com> wrote: Adenauer schrieb: On Sun, 17 Feb 2008 17:23:20 +0100, Werner Schneider <hvymetal@gmx.com> wrote: Adenauer schrieb: On Tue, 12 Feb 2008 17:56:48 +0100, Werner Schneider <hvymetal@gmx.com> wrote: Adenauer schrieb: On Thu, 07 Feb 2008 00:41:21 +0100
Yes, you can safely assume that a "serviceclassname" for kerberos is completely unrelated to a web service name. The serviceclassname is used by kerberos to compose the SPN. Kerberos uses SPNs and UPNs when referring to tickets, where: SPN = Service Principal Name in the form name/fqdn UPN = User Principal Name in the form username@domain The username@domain, or domain\username is the user
The service can be any, it has no relationship with the fact you are build a WebService. The term service, here, is not the same for both scenarios. In kerberos you ask for "service" tickets. The SPN service name, when the client is a browser is always http, so IE when accessing: http://foo.mycompany.com would ask for SPN http/foo.mycompany.com However, if the client of your service is
