Re: RE : [Tsp-devel] A small TSP provider DLL (with a Labview example )

[Eric Noulard]

2007/5/24, LAROCHE, Jean-Francois <address@hidden>:
> But, I have two questions :
>
> 1) Is the STUB_GLU_get_ssei_list_fromPGI function mandatory in this DLL ?
> (it is never called in my tests)

SSEI = Sample Symbol Extended Information
this NOT mandatory but it may be useful if you want to retrieve
meta-informations about TSP symbols, like the unit.

For example if you launch the stub_server then you may use
tsp generic consumer like this:

******
> tsp_request_generic tsp_request_extended_information 1000
tsp_request_generic: TSP provider URL is <localhost>
Request Open successfully sent to : <rpc://localhost/StubbedServer:0>
Obtained channel Id : <4>
Extented info list <begins>
   Extended info for PGI <1000> <begins>
       key=unit, value=a
   Extended info for PGI <1000> <ends>
Provider <symbols list end>.
Request Close successfully sent to <rpc://localhost/StubbedServer:0>
******

For more information on tsp generic  consumer you may read the
"TSP Design and Programming Guide" §11.2.1

http://download.savannah.nongnu.org/releases/tsp/documentations/tsp_programming_guide-1.1.pdf


> 2) I have checked this DLL with the tsp_stdout_client, and when I tried to use 
> other symbol types than TSP_TYPE_DOUBLE, the DLL provider seems to work, but 
> the tsp_stdout_client can't retrieve these parameters.
> It seems that the tsp_stdout_client is coded to retrieve TSP_TYPE_DOUBLE symbols

True stdout wasn't updated for multi-type :))
Any contribution is welcomed.

> (according to what I saw in the debugger). If yes, how can I quickly
validate my DLL
> provider with other symbol types ?

tsp_request_generic (not for sampling but for verifying TSP_request_xxx)
targa (but not for array)
tsp_ascii_writer
tspfs
tsp_gdisp (not a very good test though since it handles multi-type but
convert the value to double)


--
Erk