Antonio Gallardo wrote:
OK. Perhaps the sample is not the best, lets forget about the database.
The fact is that selection list is requesting the pipeline per row. Hence,
triggering all the pipeline and all the process that it involves. And
there is where I see a waste of time. In the static selection list, this
does not happen at all. Cforms read the data once and then serve from is
own store or cache. I think this is a lot time faster.
Well, yes. Invoking a pipeline per row would be awful.
In fact I am using OJB and since I am the only user (I am testing in my
own machine) I know the data are cached from the OJB cache. There is no
direct request to the database, where BTW, there are also cached (Again, I
am the only user). But this is still slow to my taste. Please don't
answer: "Just buy a faster processor and more RAM!". ;-) lol.
No, I agree with you.
If that is cached would the amount of time DSL
takes matter?
This is one of my concerns. And one of the reasons of my initial mail. I
guess we can save some time by triggering the pipeline only once per
request, storing the data somewhere in the selection list, and then next
row will be served from the temporal cache. Thinking in that, it must be a
lot times faster.
I admit I have been wanting to get into CForms for a while. But what you
are proposing makes sense to me.
Best Regards,
Antonio Gallardo.
