Closed torbjornlager closed 10 years ago
Works for me. CORS surely is not related as this is a client thing and the Prolog client doesn't do any CORS checking. Network down?
No, don't think so. This is what I get if I debug:
?- debug(pengine(_)). true.
?- pengine_rpc('http://pengines.swi-prolog.org', p(X), [ src_list([p(b), p(c), p(d), p(e)]) ]). % Reply to main: output('c9d92656-a150-42f2-9941-0a6ae87c90fe',"\n\n<pre class=\"msg-error\">\nArguments are not sufficiently instantiated\n\n\n") % Received output('c9d92656-a150-42f2-9941-0a6ae87c90fe',"\n\n<pre class=\"msg-error\">\nArguments are not sufficiently instantiated\n\n\n")
We should wait to see with this one though. I just remembered that I wasn't able to install pl-dev from source and my pengines.pl may therefore not be fresh enough.
Could well be (that you need the latest version). Lots of things have changed. Most people seem to manage compiling it from source. It is practically inevitable for collaboration this close to the system.
An rpc request to a server that is not CORS enabled just hangs. Example
?- use_module(library(pengines)). ?- pengine_rpc('http://pengines.swi-prolog.org', member(X, [a,b]), [ ]).
We could probably do better?