From anupamajm at gmail.com  Fri Mar 23 02:59:13 2007
From: anupamajm at gmail.com (Anupama Joseph)
Date: Fri, 23 Mar 2007 12:29:13 +0530
Subject: [Ruby-informix-misc] Packet decode for Informix
Message-ID: <d70e91210703222359g2e81d116n986587e8f0228fa1@mail.gmail.com>

Hi All

I have installed the Informix Dynamic Server 10.00 version
and the client used is the DB-Access utility.

Can anybody inform me about the packet structure for Informix.
Decode for the packets which goes over TCP.

I could just identify that the second byte in the request can be a code
which maps to a function.
Could anyone give more information on this?
Is there any way to identify the response from the server corresponding to a
request?
The format of the response data from the server

Please give me any suggestions

Thank u
Anj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ruby-informix-misc/attachments/20070323/9c004bef/attachment.html 

From jonathan.leffler at gmail.com  Tue Mar 27 11:42:58 2007
From: jonathan.leffler at gmail.com (Jonathan Leffler)
Date: Tue, 27 Mar 2007 08:42:58 -0700
Subject: [Ruby-informix-misc] Packet decode for Informix
In-Reply-To: <d70e91210703222359g2e81d116n986587e8f0228fa1@mail.gmail.com>
References: <d70e91210703222359g2e81d116n986587e8f0228fa1@mail.gmail.com>
Message-ID: <844b8e1c0703270842g12467560s7b4227aa19772c76@mail.gmail.com>

On 3/22/07, Anupama Joseph <anupamajm at gmail.com> wrote:
>
> I have installed the Informix Dynamic Server 10.00 version
> and the client used is the DB-Access utility.
>
> Can anybody inform me about the packet structure for Informix.
> Decode for the packets which goes over TCP.
>
> I could just identify that the second byte in the request can be a code
> which maps to a function.
> Could anyone give more information on this?
> Is there any way to identify the response from the server corresponding to
> a request?
> The format of the response data from the server
>
> Please give me any suggestions
>

There is no formal documentation.  The first two bytes of the packet - it is
a word-oriented protocol rather than byte oriented - are generally the
operation, with supporting data following.  The connection messages have a
wholly different, completely baroque (if not rococo) structure.  Strings are
usually preceded by their size, and are (usually if not always) null padded
to an even length.  For the rest, you'll have to do some research - sorry.

-- 
Jonathan Leffler <jonathan.leffler at gmail.com>  #include <disclaimer.h>
Guardian of DBD::Informix - v2007.0226 - http://dbi.perl.org
"I don't suffer from insanity - I enjoy every minute of it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/ruby-informix-misc/attachments/20070327/24f42d17/attachment.html