View Single Post
Old 07-18-2010, 03:33 AM   #45
rollercoaster
Zealot
rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.rollercoaster once ate a cherry pie in a record 7 seconds.
 
rollercoaster's Avatar
 
Posts: 126
Karma: 1826
Join Date: Jan 2010
Device: Kindle 2
Quote:
Originally Posted by Starson17 View Post
Calibre's recipe system isn't set up at this low level of sending GET/POST. It operates at a higher level.
I dont understand. GET/POST are not low lever operations. A quick search for "python POST request" shows me many examples of people doing this. e.g -

pass a data keyword argument to urllib.urlopen:

u = urllib.urlopen('http://www.domain.com/cgi-bin/cgi.py',
data=urllib.urlencode({'name': 'pythonguy'}))


POST is the way to submit form data. For e.g. Username password forms. The main difference with GET (any normal read url request) is that the parameters are submitted as multi-part form-data instead of in the query string and are not limited in size as URLs usually are.


Quote:
Originally Posted by Starson17 View Post
Sorry to disappoint you, but I'm going to focus on a couple of other things of interest to me in Calibre code.
That is too bad but I can understand the limitations.

Thanks very much for you time though. May be we can pick this up later sometime. Recipes could do with more advanced features like additional UI elements and more control over the whole fetch process.
rollercoaster is offline   Reply With Quote