Subject: SOCKIT experimentation
In-Reply-To: <CAAbtOZf90Tvnj4d=byP59A1KktAccLPoFcK7ER6=18gKH_HhZw@mail.gmail.com>
References: <c118ed45-e109-2465-2810-727b63587bb0@colostate.edu>
<CAAbtOZdU252kpRK5qssqv_GbGgWmF6Kt+3Pkgyru86pmJUo5Uw@mail.gmail.com>
<be954704-8078-9d34-fb7e-1c0ab239ed40@colostate.edu>
<CAAbtOZf90Tvnj4d=byP59A1KktAccLPoFcK7ER6=18gKH_HhZw@mail.gmail.com>
Message-ID: <cb9f941f-2463-ef1b-ac2b-37024737b439@colostate.edu>

Andy,

Thanks for your additional suggestions.

I thought your suggestion of a "positive control" as you previously described to be a very good one so I ran it. And it ran successfully. :)

What I realized from running this and your earlier message was that the textWave was being filled as you wrote in the ****LAST**** row which I couldn't see because of the sizeable zeroth dimension I started with on the wave. Doh!

SOCKIT works just fine even with my own (non-http) server and all the advertised functionality also appears to be working OK also.

Thanks again for the able assistance.

Best regards,
Joseph

On Thu, 28 Mar 2019 2:53 PM, Andrew Nelson wrote:
> Joseph,
> if you're getting the messages being printed out in the command window,
> that's good because the messages are actually being received. The messages
> should be automatically placed in the text bufferwave you provide, always
> filling out the last row. SOCKIT was not specifically designed for
> request/response, it was designed for synchronous and asynchronous (i.e.
> your situation) communication. There may be an upper limit as to the volume
> of material it can process though.
>
> 1) It may be worth trying to use the example I gave because it showed that
> at the raw socket level the thing actually works, and that the message was
> going into a wave. Any communication via TCP sockets is just stuff coming
> in and out. Only when you get to a protocol (e.g. http) does it matter what
> order stuff happens in and what the messages are.
> 2) Make sure you haven't set the /NOID flag.
> 3) Try making the connection without the /PROC flag to start with. The
> messages should just pile up in the bufferwave. What precisely is the
> remote server sending? If it's binary instead of text then a table may not
> display them.
> 4) If step 3 works then try using a processor function. Make sure the
> procedures are compiled otherwise nothing will happen.

--
Joseph A. DiVerdi, PhD, MBA
Associate Professor of Chemistry
Colorado State University
+1.970.980.5868 - http://sites.colostate.edu/diverdi