Quote:
Originally Posted by raztoki
@Lelim
Think the way captchatrader solved that issue (last time I used CES and JD was that far back), was to rename images based on some internal id, that way you are not limited by a single filename restriction.
jac > script > exe/jar/whatever > copies input image and indexes, removed image > submits image into API, returns info based on index and passes answer to the correct download. Think that was the gist of it.
JAC is not documented that I'm aware of, it does have many established pitfalls.
The best bet would be people migrate to JD2, and use the native CES solution provided.
|
yes, i thought of renaming the input.jpg with process id, but when i create an output file, since its name is set in the jacinfo.xml, all running processes will try to open it and read the answer. on output file, i think we will still be restricted on single filename i guess..
i agree with jd2, is there a plan on your side to force users to upgrade to jd2 on a specific time?