Actually, thats a damn good point, I use Google Maps on some of my websites,
and yet I gave that answer to you, perhaps they're using Iframes? Anyone
have an answer for this, now you got me interested!

- jake

On 3/16/07, bruce <[EMAIL PROTECTED]> wrote:

 jake...

if what you state is true. how does google/yahoo/flickr/etc... manage to
allow 3rd party websites to access their hosted apis, which are resident on
the hosted server of google/yahoo/etc....


-bruce


-----Original Message-----
*From:* Jake McGraw [mailto:[EMAIL PROTECTED]
*Sent:* Friday, March 16, 2007 9:17 AM
*To:* [EMAIL PROTECTED]
*Subject:* Re: [jQuery] php - web service (ajax/jscript)

Bruce,

I believe, regardless of the website serving the Javascript file, AJAX
will only interface with the server that actually served the entire
document.

What I suggest you do is provide clients with a PHP Script / HTML Template
(Smarty is very good for this) with some AJAX Javascript.

The PHP Script can contact your web service (you can use the PEAR
SOAP/WSDL extensions or go for the full blown Tomcat/Apache config), serve
whatever information you like back to the PHP Script and then back to the
browser:

Request
Web Browser/AJAX -- (XML or JSON) --> Client Server/PHP/SOAP -- (XML) -->
Your Server/(PHP or Tomcat)

Return
Your Server/(PHP or Tomcat) -- (XML) --> SOAP/PHP/Client Server -- (XML or
JSON) --> AJAX/Web Browser

So basically, your clients would need a web server that handles PHP and
can make SOAP Requests, you would author the PHP/HTML template and release
that as an "api". This is probably the best way to go about things because
it allows non-web browsers user access to your Web Service and it keeps with
the whole concept of what web services should truly be.

- jake


On 3/16/07, bruce <[EMAIL PROTECTED]> wrote:
> Hi Jake.
>
> Thanks for the reply. I'll try to clarify. (Keep in mind, I'm not an
> experienced web developer!)
>
> As I understand Ajax, it's used to allow asynch interaction between
client,
> and hosted site that the client js file is fetched from. In other words,
if
> the client html/php has something to the effect:
>
>   <html>
>   <script>
>   <src = 'http://www.homeserver.com/test.js'
<http://www.homeserver.com/test.js%27>>
>   </html>
>
> Even though the client html/php might be on the 'foo' site
> (www.foo.com/test.html), the test.js functionality is being served from
the
> 'homeserver.com' domain, and can therefore interface/communicate with
the
> 'homeserver'. This is what I want to accomplish, as it allows me to
create
> test servers/apps, and they can each communicate via the test api/web
> service (on homeserver.com) with the homeserver web service.
>
> so i'm trying to get my hands around how to create/implement a test app
to
> demonstrate this. A rough overview is:
>
>  Assume:
>     Master Server                        3rd Party Server (separate
domain)
>       App1                                   Test App
>       API File                               (aa.js) (from Master
Server)
>       JScript (aa.js) ------>>-----------------^
>
>  The aa.js file allows the 3rd party client site to be able to interface

> with
>  the Master Server API via the API/services defined in the API File. I'm
>  envisioning the following actions for the user
>
>    3rd Party Site                       Master Server
>       -User Enters Name >>>>>>>>>>>>>>    api checks/verifies name
>       -gets response
>         Master Server    <<<<<<<<<<<<<<   returns response
>       -user answers
>        question based
>        on response,
>        sends response
>        to master server
>        via api          >>>>>>>>>>>>>>   api checks user input
>       -gets response
>         Master Server    <<<<<<<<<<<<<<   returns response
>       -jscript then
>        gives reply/response
>        to the 3rd Party site,
>        allowing the site/app
>        to continue processing
>
>  In this case, the jscript/ajax app is really only communicating with
the
>  Master Server, which if I understand it correctly would be in the same
>  domain as the ajax/jscript code. In other words, if the master server
>  supplies the jscript file(s) for the jscript that's to be run on the
3rd
>  party server, then any communication that's initiated from the jscript
is
>  going back to the master server. There shouldn't be a cross domain
issue?
>  Yes/No???
>
> So I'm trying to find docs/help/information (someone to talk to) so I
can
> create a test app that accomplishes this kind of functionality.
>
> Thanks
>
> -Bruce
>
>
> -----Original Message-----
> From: Jake McGraw [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 16, 2007 7:07 AM
> To: [EMAIL PROTECTED]; jQuery Discussion.
> Subject: Re: [jQuery] php - web service (ajax/jscript)
>
>
> Bruce:
>
> I'm not sure I fully understand what you are trying to accomplish, but
> AJAX is not a replacement for SOAP/WSDL Web Services as it is strictly
> limited to communication within its own domain, which flies in the
> face of Web Services philosophy.
>
> Could you provide a more concise example of what you would like to do?
>
> - jake
>
> On 3/15/07, bruce <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I'm trying to find information with regards to how to create/implement
a
> > test web services app. I'm trying to find pointers to anyone who's
> actually
> > created this kind of functionality, or pointers to web sites where I
can
> > find the information I'm looking for.
> >
> > For my test, App1 has the web service, and provides the jscript/ajax
code
> to
> > the 3rd Party, for use on the Test App. I'm trying to find php code
for
> the
> > apps on the web servers as well as test php code for the api on the
Master
> > Server. I'm also trying to get/find a test situation that provides
test
> > client code (jscript/ajax) to be implemented on the test server/app.
> >
> > Assume:
> >    Master Server                        3rd Party Server (separate
domain)
> >      App1                                   Test App
> >      API File                               (aa.js) (from Master
Server)
> >      JScript (aa.js) ------>>-----------------^
> >
> > The aa.js file allows the 3rd party client site to be able to
interface
> with
> > the Master Server API via the API/services defined in the API File.
I'm
> > envisioning the following actions for the user
> >
> >   3rd Party Site                       Master Server
> >      -User Enters Name >>>>>>>>>>>>>>    api checks/verifies name
> >      -gets response
> >        Master Server    <<<<<<<<<<<<<<   returns response
> >      -user answers
> >       question based
> >       on response,
> >       sends response
> >       to master server
> >       via api          >>>>>>>>>>>>>>   api checks user input
> >      -gets response
> >        Master Server    <<<<<<<<<<<<<<   returns response
> >      -jscript then
> >       gives reply/response
> >       to the 3rd Party site,
> >       allowing the site/app
> >       to continue processing
> >
> > In this case, the jscript/ajax app is really only communicating with
the
> > Master Server, which if I understand it correctly would be in the same
> > domain as the ajax/jscript code. In other words, if the master server
> > supplies the jscript file(s) for the jscript that's to be run on the
3rd
> > party server, then any communication that's initiated from the jscript
is
> > going back to the master server. There shouldn't be a cross domain
issue?
> > Yes/No???
> >
> > So, anyone who's actually implemented a real live web service, that's
> > willing to talk to me would be helpful, or if you can point me to
sample
> > docs/code...
> >
> > Thanks
> >
> > -bruce
> >
> >
> >
> > _______________________________________________
> > jQuery mailing list
> > discuss@jquery.com
> > http://jquery.com/discuss/
> >
>
>


_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Reply via email to