The request may have references to objects that will no longer exist, or may be inappropriate when rerun later. I can't promise that it won't work, but I believe that pickling the request is at best a fragile solution.
To save just the required parameters won't take much code, especially if you refactor the code that turns the parameters into a the search operation into a function (or method) that you can use both initially and when you rerun the search. Having to do some preparation again probably isn't going to be as big a performance drain as unpickling enough context to make it work without extra code. On Wed, Apr 28, 2010 at 11:56 AM, Mark Jones <mark0...@gmail.com> wrote: > I was thinking I could pickle/unpickle the request then run it thru > with an extra flag of (send email) thru the same code that wsgi uses. > If I jsonify the data, how would I get that back into a python object? > > Is it really as simple as str=json.dumps(request) and request = > json.loads(str) > > I don't see how json keeps track of the object it is dumping, and not > sure how to construct a request object from the json return value. > > I can see how easy that part would be in C++, but my python skills are > a good deal weaker.... I guess I'm hunting for "how to do this in > python" > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
