search

vspinu / betfairly

R betfair api
2 stars 3 forks source link

Error: XML content does not seem to be XML: 'close 410 Gone #1

Open Jax471 opened 10 years ago

Jax471 commented 10 years ago

Hello,

I am getting the following error when I using betfairly package to connect to betfair (It was working fine till 12 hours back. All of a sudden it is not working. Is it because of a change in betfair output?)

Error: XML content does not seem to be XML: 'close 410 Gone

I am copying below R and betfairly configuration

Regards, Jax

sessionInfo() R version 3.1.1 Patched (2014-07-18 r66202) Platform: i686-pc-linux-gnu (32-bit)

locale: [1] LC_CTYPE=en_US.utf8 LC_NUMERIC=C
[3] LC_TIME=en_US.utf8 LC_COLLATE=en_US.utf8
[5] LC_MONETARY=en_US.utf8 LC_MESSAGES=en_US.utf8
[7] LC_PAPER=en_US.utf8 LC_NAME=C
[9] LC_ADDRESS=C LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.utf8 LC_IDENTIFICATION=C

attached base packages: [1] stats graphics grDevices utils datasets methods base

library("betfairly") Loading required package: RCurl Loading required package: bitops Loading required package: XML sessionInfo() R version 3.1.1 Patched (2014-07-18 r66202) Platform: i686-pc-linux-gnu (32-bit)

locale: [1] LC_CTYPE=en_US.utf8 LC_NUMERIC=C
[3] LC_TIME=en_US.utf8 LC_COLLATE=en_US.utf8
[5] LC_MONETARY=en_US.utf8 LC_MESSAGES=en_US.utf8
[7] LC_PAPER=en_US.utf8 LC_NAME=C
[9] LC_ADDRESS=C LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.utf8 LC_IDENTIFICATION=C

attached base packages: [1] stats graphics grDevices utils datasets methods base

other attached packages: [1] betfairly_1.2.2 XML_3.98-1.1 RCurl_1.95-4.3 bitops_1.0-6

vspinu commented 10 years ago

This might be a change in betfair api but most likely a temporary glitch. Or you were blocked from betfair. You should investigate the raw response.

Unfortunately I cannot look into this as I am now in US from where betfair is blocked.

Jax471 commented 10 years ago

Hi Vitalie,

Thank you for the prompt reply.

I hope that it is a temporary glitch and that betfair fixes it soon. I have contacted them.

If it is not, could you please suggest to me how I should go about investigating the raw response - what articles should I read to learn the procedure to do so.

Regards, Jax

Jax471 commented 10 years ago

Hello Vitalie,

Betfair has responded to my message mentioning that it is because they released new API on November 14th, so the error.

Could you please go through the documentation, which I have sent to your e-mail, and release new version.

Thanks, Jax

vspinu commented 10 years ago

I am afraid their new api is really "NEW". It's a massive change and would require complete rewrite of the betfairly package.

I might be able to look at it only after I am back to Europe by the end of the Januarry. But I am unlikely to do that for two reasons. First, R is not a good language for web applications and you would be better implementing your bots in any other general purpose scripting language Second, I am not using betfairly myself and I am too busy with other projects. Sorry to disappoint but, I have to declare this project dead.

Jax471 commented 10 years ago

Hello Vitalie,

Thanks for the prompt reply.

I agree with you that R is probably not a good language for web applications. But, it is good software for statistical computation, which is the real intelligence part of the solution. After that, it is ok to have a working API.

I hope that you can work on releasing a new package for the new API, whenever you have time.

Thank you for providing the package and support.

Regards, Jax