Selon Peer Sommerlund <peer.d.sommerlund@...>:

> This is sort of what I had in mind. However, your AJAX must send the
> move to the server somehow. I figured that I could use the same
> interface. No need for me to build a web service.
>
Yeah, it sends the moves by calling a web service :) i.e in our case it's
calling an URL with specific parameters ... like

http://nacre.com/ilovepeer/getmove.asp?move=a1b1

and your web server returns an XML flow giving the answer from your engine.

all you would need is a web server, and a web page that takes the parameters
from the query string in the URL, and returns an XML response. The query string
can be a little more complicated (i'm using a microsoft like web services), but
not that much :) Calling any process on your web server with the protocol you
love is fairly easy. even PHP under Unix and Apache...

btw building a web service is also pretty easy lol.

My idea is definitely not to have nacre running on your PC with some interface
between my AJAX (on the client) and the nacre engine like you usually do with
NetAbalone, i dont want to call some TCP/IP socket protocol (eg abnet). This
would be a lot more complex than simply calling an URL (we are in 2006 lol, no
more 68000 assembly please).

I also want this to comply with both firefox and IE and be pure javascript on
the client (no java, no activeX, no download, no security issue, no popup
blocker and so on). i.e. comply with the tech rules i've set for my server
since oct/sept this year.

david