Callback job_start()

This callback is called when the framework has received a printing job. It already has checked if it can deal with the document data format, e.g. a corresponding rasterizer is already attached and now it is up to you to check if this job can be printed on your printer.

• parameter you get
  • framework handle
  • your private data hint
• you can expect as already done
  • everything is working as expected, e.g. communication with the printing coordinator and the printer device
• what you can do
  • everything you need to do to process data
• what you must do
  • you must check if this job can be printed on your device
    • medium format settings
    • resolution settings
    • colour/grey/monochrome setup
    • simplex/duplex settings
    • and so on
• values you should return
  • 0 everything is okay, the framework can continue
  • -EINVAL if the job cannot be printed.
    • the job will be canceled and the job_finish() callback is called next
  • -EBUSY The printer is somehow busy (more or less a printer error condition, cover opened for example)
    • TODO makes no sense here
  • -EBADMSG ?
  • -ENODEV It isn't the expected printing device or something else is bad with this device and the framework should terminate

Functions related to this state:

• Retrieving information about the job to print

  Todo:

  Job status updating in case of a failure.

  We need to distinguish a bad job from a bad behaviour of the software, e.g just skip the job versus terminating the driver