Michael R Sweet

@zhulisong I personally have not done so, and I know certain features just don't work on Windows due to differences in that OS (particularly the pipe support for print commands).

@zhulisong ippserver is *sample code* and comes with absolutely no support, warranty, etc. Furthermore, the whole ippsample project is absolutely *not* intended for production use - it is prototyping code....

I can't see using the ppdc format, which doesn't even support this sort of thing... Putting in the Future milestone (not 1.0) for now, as I'm not sure how to...

Get-Notifications only reports new events AFTER the subscription is created. Get-Jobs with which-jobs='fetchable' should prime things in ippproxy, checking...

Yes, the spec is pretty clear about the startup sequence for proxies so they can sync up the state of existing jobs...

The notification is working, but ippproxy isn't doing an initial Get-Jobs with which-jobs='fetchable'... Plus it doesn't retry or abort the job if things go wrong... Need more error handling for...

OK, think I have this fixed now.

ippproxy wasn't updating the job status to say it was completed.

In fuzzing/grease mode we need to make sure we report/record the actual IPP message so that bug reports, etc. can include the full request for testing and debugging.

Feedback from morning IPP session: - Should also include ippserver - Perhaps use a separate ipptool file generator for the fuzzing - GREASE support likely needs to be made part...