Support Board
Date/Time: Fri, 29 Nov 2024 03:49:10 +0000
sc.MakeHTTPRequest()
View Count: 1439
| [2019-04-29 08:16:21] |
| User864893 - Posts: 26 |
|
I have written several studies for the convergenttrading community. Some of them load levels from the community servers by using sc.MakeHTTPRequest(). When HTTP requests are made there are those statements logged into the message log. ESM19 15 Min #2 | Study: StalkZones | Making HTTP request. | 2019-04-29 09:53:12 HTTP connection ID:12 to xxxx.convergenttrading.com:80 for request ID:12 (3) | Creating socket. | 2019-04-29 09:53:12 HTTP connection ID:12 to xxxx.convergenttrading.com:80 for request ID:12 (3) | Connecting to IP: A.B.C.D. | 2019-04-29 09:53:12 HTTP connection ID:12 to xxxx.convergenttrading.com:80 for request ID:12 (3) | Shutdown started. Waiting for graceful close. | 2019-04-29 09:53:12 HTTP connection ID:12 to xxxx.convergenttrading.com:80 for request ID:12 (3) | Socket gracefully closed by remote side. | 2019-04-29 09:53:13 HTTP connection ID:12 to xxxx.convergenttrading.com:80 for request ID:12 (3) | Closed. | 2019-04-29 09:53:13 (IpAdress & servernames removed above) Is there any possibility to disable this log messages as some users complaining about the amount of logmessages. By default the requests are made every 5 mins and this gives a huge amount of messages in the message logfile. If no possibility is there yet, could you add a parameter / flag to the sc-structure to disable for example sc.DisableHTTPLogMessages. Thanks a lot |
| [2019-04-29 15:32:14] |
| |
|
We will work on a solution to this. Just give us a couple of days.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2019-05-20 09:47:49] |
| User864893 - Posts: 26 |
|
Can i ask whether there is already a solution implemented ? Thanks
|
| [2019-05-20 10:02:20] |
| |
|
No not yet. We were going to say this is being delayed because there are many details we need to think through when implementing a solution. We will try to get to it this week. It is not going to take weeks.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2019-06-03 23:48:16] |
| |
|
This has not been forgotten about . It is just involved for us to do this right.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2019-07-16 07:56:47] |
| |
|
We acknowledge this is actually very involved to do properly. And it is taking weeks for us to get to it. We are doing a little at a time though.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2019-07-17 21:09:51] |
| |
|
This is now done in version 1952. Only the HTTP connectivity errors will be reported. There still is more work for us to do but the basic work is done.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-03-13 05:07:40] |
| User900285 - Posts: 94 |
|
Hello, Sorry for replying to a very old thread but what is the method for removing the HTTP request log messages from the Sierra Chart message log? These messages appear in the message log when a study makes a HTTP request. They are good for debugging but I would like to remove them at some point. I am using the sc.MakeHTTPPostRequest() function. |
| [2023-03-13 16:35:38] |
| ForgivingComputers.com - Posts: 960 |
|
AFAIK, The message log cannot be edited, but it is limited in size to something like 10,000 lines, so it will not keep growing forever.
|
To post a message in this thread, you need to log in with your Sierra Chart account: