A
atuldalvi123
Guest
Actually the old programs are designed in such a way where they are unnecessary hitting DB & creating records in the tables in each web service call even before the actual policy creation just to show some information on the next page. For example, on the 1st page itself when we put customer information and proceed for the next page, data gets created in the tables such as account information and many more just to show information on the next page and just like this for every next page we have web service calls and DB hits till the last page which is causing the issues. These DB hits are not only for the couple of table data population but to read couple of master tables as well. So we are planning to restructure the progress code but it is not easy for us as of now and so we are looking for the memory related concept in progress programming ( Not HTTP level ) where we can skip these DB hits in between.
Continue reading...
Continue reading...