List Info

Thread: server size YAZ




server size YAZ
user name
2007-02-27 07:29:13

When you are setting up a YAZ service, is there any way to stop the API from deleting a request past the scope of the registered method?

For instance, you pass in bend_esrequest_rr *rr into the registered method. If I queue that object, but the method returns, the API cleans it all

up and rightly so. Is there a way to tell it not to destroy the PDU that rr points to? Or conversely, is there an easy-ish way to deep copy that structure?

 

Thanks

Daine. (:

 

server size YAZ
user name
2007-02-27 11:43:53
Daine Mamacos writes:
 > When you are setting up a YAZ service, is there any
way to stop the
 > API from deleting a request past the scope of the
registered
 > method?
 > 
 > For instance, you pass in bend_esrequest_rr *rr into
the registered
 > method.  If I queue that object, but the method
returns, the API
 > cleans it all up and rightly so. Is there a way to
tell it not to
 > destroy the PDU that rr points to? Or conversely, is
there an
 > easy-ish way to deep copy that structure?

What structure are you wanting to preserve, exactly?  If
it's
Z_TaskPackage *taskPackage (or any of the other types whose
names
begin with "Z_") then the easiest way to make a
persistent copy is to
serialise it into a temporary ODR object, then immediately
read a copy
back out (and then destroy the ODR that contains the
serialisation).

 _/|_	
____________________________________________________________
_______
/o ) /  Mike Taylor    <mikeindexdata.com>    http://www.miketaylor.or
g.uk
)_v__/  "Revise and rewrite" -- Strunk &
White.


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list

Re: server size YAZ
country flaguser name
Denmark
2007-02-27 20:04:28
Daine Mamacos wrote:

> When you are setting up a YAZ service, is there any way
to stop the 
> API from deleting a request past the scope of the
registered method?
>
> For instance, you pass in bend_esrequest_rr *rr into
the registered 
> method. If I queue that object, but the method returns,
the API cleans 
> it all
>
> up and rightly so. Is there a way to tell it not to
destroy the PDU 
> that rr points to? Or conversely, is there an easy-ish
way to deep 
> copy that structure?
>
>  
>
> Thanks
>
> Daine. (:
>

I haven't analyzed this thoroughly, but I think it's
possible that if you
call odr_extract_mem on the 'decode' stream that you get
from a given _rr structue
in the frontent server, you can keep data allocated on that
stream from annihilation.
odr_extract_mem will return a handle that you have to
preserve somehow. Call odr_release_mem
on it when you're done with it. More at http://ww
w.indexdata.dk/yaz/doc/odr.use.tkl .

Cheers,

--Sebastian

>  
>
>--------------------------------------------------------
----------------
>
>_______________________________________________
>Yazlist mailing list
>Yazlistlists.indexdata.dk
>http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
>  
>

-- 
Sebastian Hammer, Index Data
quinnindexdata.com   www.indexdata.com
Ph: (603) 209-6853 Fax: (866) 383-4485


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )