From: Dmitry Y. <fir...@ya...> - 2010-01-15 13:17:30
|
Adriano, >> Another related thing (from memory, so I may be imprecise) could be to >> still parse the (non-null) output sqlda but don't recreate the output >> message every time. > > ... > >> Just compare the current sqlda with the priorly used >> one and reuse the last message if sqlda hasn't changed. >> > I thought on storing the last sqlda value and comparing it with the passed one, and totally skip the UTLD call. > > It would make applications faster automatically, but there will be a potential problem, if the user pass the same sqlda with something changed. I don't think users are doing that, but is something valid currently. > > Do you mean the same thing? Supposedly, yes :-) But I don't see what "something" can be changed by the user for the output sqlda. The destination address? We could ignore it when comparing two sqlda's for "equality" but still use it when copying the returned data from the message. Dmitry |