Getting started on FIX protocol with PHP sockets

I have pretty basic knowledge of PHP sockets and the FIX protocol altogether. I have an account that allows me to connect to a server and retrieve currency prices.

I adapted this code to connect and figure out what I receive back from the remote server:

$host = "the-server.com";
    $port = "2xxxx";

    $fixv = "8=FIX.4.2";
    $clid = "client-name";
    $开发者_C百科tid = "target-name";

    $fp = fsockopen($host, $port, $errno, $errstr, 30);
    if (!$fp) {
        echo "$errstr ($errno)<br />\n";
    } else {
        $out = "$fixv|9=70|35=A|49=$clid|56=$tid|34=1|52=20000426-12:05:06|98=0|108=30|10=185|";
        echo "\n".$out."\n";
        fwrite($fp, $out);
        while (!feof($fp)) {
            echo ".";
            echo fgets($fp, 1024);
        }
        fclose($fp);
    }

and I get nothing back. The host is good because I'm getting an error when I use a random one. Is the message I'm sending not generating a reply ?

I might not be very good at finding things in Google but I could not find any simple tutorial on how to do this with php (at least nothing that puts together fix and php).

Any help is greatly appreciated.

---

FIX separator character is actually '\001' not '|', so you have to replace that when sending.

Some links for you:

• FIX protocol - formal specs
• Onixs FIX dictionary - very useful site for tag lookup

Edit 0:

From that same wikipedia article you mention:

The message fields are delimited using the ASCII 01 character.
...
Example of a FIX message : Execution Report (Pipe character is used to represent SOH character) ...

Edit 1:

Couple more points:

• Tag 9 holds message length without tags 8 (type), 9 (length), and 10 (checksum).
• Tag 10, checksum, has to be a modulo 256 sum of ASCII values of all message characters including all SOH separators, but not including the tag 10 itself (I know, it's stupid to have checksums on top of TCP, but ...)

---

The issue is the use of fgets(...), it is expecting a \n which does not exists in this FIX protocol.

On top of that, an expected length of 1024 is specified, which is a length that the response is unlikely to exceed.

To cap it off, since the server doesn't terminate the connection, fgets(...) hangs there "forever"