Greetings. Please find below e list of consultants currently available for projects. Your Help is Highly Appreciated
My Sincere Request: Kindly add my Email mailto:[EMAIL PROTECTED] in your distribution list and it would be a great honor for me to work on your requirements. *NAME* *SKILLS SET* *YEARS OF EXPERIENCE* *LOCATION* *RELOCATION* Narayan SAP HR 7+ TX Open Sridhar Dot Net 7+ Chicago Open Latha Dot Net 6+ Chicago Open Swapna Dot Net 6+ CA Open Kiranmyee Dot Net 6+ OH Open Vivek QA 7+ Virginia Open Jaina QA 7+ Stamford Open Sarada QA 6+ Boston Open Dayakar QA 7+ PA Open Pradeep PL/SQL 7+ CA Open Sreenivas BW/BI 7+ CA Open Jignesh BW/BI 6+ IL Open Sandhya BO 7+ CA Open * * * * * * *Looking forward to work with you.* *Thanks Krishna CSR SYSTEMS INC [EMAIL PROTECTED] Phone::508-425-7380 Fax ::508-425-7417 www.csrsystem.com* --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "New Hampshire Jobs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visie retrying/sleeping in the backgroundrb worker > in order to try to wait it out until the record is there. This seems > to me a last resort. Would love to hear what your experiences are and > of a better solution if it exists. > Yes, this issue came up before on the list and mostly went unresolved. I think, this is especially true for databases thats remotely located (I am unable to reproduce this with my local test setup). Currently your best bet is to retry, something like this can be a good idea: def foobar ar_id t = User.find(ar_id) unless t # better than sleep, because your worker can # process other requests while this timer gets ready add_timer(1) { foobar(ar_id) } else # do the normal processing here end end _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
