Announcement

Collapse
No announcement yet.

esignal.ReleaseHistory(lHandle)???

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • esignal.ReleaseHistory(lHandle)???

    Hi,

    I am not sure if this "esignal.ReleaseHistory(lHandle) " function works fine.

    My program is trying to get 2000 quotes history. My limitation is set to 200 quotes. Each time, I request a quote, after I receive the data, I release it. But, still esignal is complaining that I am exceeding my limitation.

    Will you pls. check if it really releases history ?

    Thanks - Umit

  • #2
    ReleaseHistory doesn't clear the cache. You will want to call ClearSymbolCache() in there somewhere as well.

    Cheers... George

    Comment


    • #3
      ReleaseSymbolCache "MSFT"

      or

      ReleaseSymbolCache("MSFT")

      or

      ReleaseSymbolCache lHistoryHandler

      which one is correct?

      Thanks

      Comment


      • #4
        ClearSymbolCache() takes no arguments and releases everything not currently in use (i.e. not referenced by an active handle somewhere).

        esignal.ClearSymbolCache()

        Cheers... George

        Comment


        • #5
          I do not understand your issue. You have a limit of 200 symbols and you are attempting to request 2000? If you are only permitted to request 200 symbols, you will not be able to request more that 200 symbols.

          Comment


          • #6
            Robi,

            As long as I release the history handle. I can request as much as i want to.


            request history one symbol
            get the history data
            release the history handle

            These 3 lines can be looped to 2000 even if my quote limitation is set to 200.

            Is not that true.

            Umit

            Comment


            • #7
              Releasing Symbol History and Requests

              Hi,

              I am facing a similar issue. I am trying to gather historical information for about 1700 symbols but my permissions are 500. My understanding has been that if I release the symbols after collecting my data I can gather as many as I want. However, I have been calling the releaseallhistory() and clearsymbolcache() methods of the eSignal object to no avail.

              This is tough because there is no clear documentaion for these types of examples and it seems that maybe we are the only people trying to do this.

              feel free to send me a private message and perhaps we can work through this together.

              Comment


              • #8
                Are you guys seriously describing how to hack our API on a forum hosted by us?

                We know of the loophole with RequestHistory, allowing more symbols to be retrieved than allowed, but also know that the limitation is more strongly enforced with quote data because that is the data that we are most concerned about. We have addressed the issue in our new version of client software and will also be adding tighter restrictions on our data servers, so if you are able to hack around now, you will not be soon.

                Robi

                Comment


                • #9
                  I didn't know that what i am trying to do is considered hacking. I did believe that it was the proper way the API was utilized. I won't continue to try this any longer.

                  Comment


                  • #10
                    Robi,

                    We are not trying to hack. I just want to understand how history release works. As long as I release 1 symbol, I should be able to request another new symbol and get the data.

                    Actually, my program works fine, I do get my data, but "the error mesagge from esignal that states i am exceeding my quote limitation" bothers me. I want to have the full understanding.Sometimes I am having this message eventhough i ask for 50 symbols while my limitation is 200.

                    Maybe in the middle of the program, I should reset my API connection.

                    set esignal = nothing
                    then
                    Set esignal = New IEsignal.Hook.......

                    Thanks

                    Comment


                    • #11
                      Robi,

                      I think your "hack" comment is inconsistent with eSignal's earlier statements and assurances.

                      Go back to thread 4859 and look at Jay's comment "That is correct. Once a symbol is released it will be removed from the symbol count assuming of course that it isn't being used by another application."

                      If a scan 500 symbols (my limit) in the morning, there is no reason why I should not be able to scan 500 different symbols in the afternoon. I have on several occasions read or been told this by eSignal, and have invested 1000+ man hours in development based on that premise.

                      eSignal has left us to our own devices on many issues like this, and we use this board to help each other navigate. "Hack" is a pretty offensive term to some of us.

                      Comment


                      • #12
                        I apologize for using the word "hack" - I didn't know political correctedness reached the technical community as well. I was just surprised to see comments on how to exceed eSignal's symbol limits posted on our forum.

                        Each RequestHistory() call places the symbol in: Data->Symbols list in the Data Manager, just like it would be a quote.

                        Bullman, what you described is fine. It is basically the equivalent of looking at 500 charts, closing them all and opening 500 more. Obviously, that is acceptable, but I will add that if you are continually making history requests, the servers "notice" you and realize you are making numerous requests and will place you at the bottom of the queue, since you are "hogging" the servers with all the requests. So if you are exceeding your symbol count by clearing the cache, you very well may notice performance issues.

                        As I stated earlier, we are more concerned with users abusing real-time quotes, or ticks, since that is what the exchanges crack down on us about, so it is much more difficult to find ways to exceed the quote symbol limit - but please do not take that as a challenge.

                        Comment

                        Working...
                        X