you can model each bot as a restful server

Then other bots need external IP to configure its as a server. (why? )
And in general this decentral system is hard to install and support

I think http based protocol and php servers is the best solution for this problem.
welcome to discuss this option.

not sure how you expect to do this without a server.

Nefton's question is this: Why does the server not provide the client with a list of available actions?

If it doesn't, then every client has to figure this out for himself. That's horrible.

Just one server. Example:

9 peoples with 7 bots want to play poker (tourney)
Do you think all of them need to rise there oun server? = 9 servers?
I think no. It must be one php server. And 9 clients. 2 from them are just html pages with java.

How setup 9 servers? 8 peoples will setup there servers and should wait (may be 1 month) when there 9th friend setup own?

And if there are 1 php server anybody can setup own client as long as he want at any time. And at the other end of the wire nobody should wait him.

Perhaps I'm not explaining this well, or misunderstanding the requirements.

I'm talking of a system whereby each bot is a server. A client application co-ordinates the two (or more) decision making servers. Think of it as the dealer. It posts the current game state to the server and the server replies with an action. In web terms this is a very common set-up. For example, a web page contains enough logic to interact with one or more servers and a user interface that allows someone to control that interaction.

Given the way in which strategies are constructed - linking gamestates to actions - it's simple for each server/bot to return the action their strategy dictates at a given gamestate/infoset. So the webpage holds the current gamestate and when it's a given bots turn to act it asks them for an action for that gamestate.

Again, maybe I'm not being clear or I've misunderstood what is required. But if I was going to design a system for multiple, disparate bots that had private logic to interact via a common, publicly available interface, that's what I'd build. (disclaimer - I design restful systems for a living)

[it could be that you mean every client has to figure out the list of possible interactions with the server, but thats' the good thing about this approach, there's only one. Each server has to do the following: translate a gamestate (in hold-em this is: board, action history, holecards, pot, possibly seating if more than HU) into an action. That's it.]

I had read ACPC protocol. It`s wery pure on my mind. Cases:
1. server can not conect to client on http.
2. grammar of request is hard to process with php page. (variables must transmit like http post request)
3. Client MUST know what in server happen. For example the are a fsm on the server with curent state.
this state based on other player moves and rules. If I wish to write java application to operate human with the server I need write the same fsm in java It wil twice my work. Why not to transmit available moves throw protocol?

Is this the sort of thing you are looking for
http://www.cubeia.org/index.php/poker
http://www.cubeia.org/wiki/index.php?ti ... rebaseBots

or just buy some java hosting service