This project has moved. For the latest updates, please go here.

Response takes too long (till 20 sec)

Jan 6, 2013 at 1:39 PM

Hey there,

first, thank you for the Libary.

But when I send an Request to TMDB, the Response lasts up to 20 sec.


Is this normal?

Feb 19, 2013 at 11:38 AM

Sorry for the late reply.

No 20 seconds isn't good. Is this still as issue for you? Any api method in particular?
Feb 20, 2013 at 10:50 PM
I have the same Problem.

In my Project, i use the last dll .
It'a a Visal Basic 2010 Express Project.

After Declearation, i have tryed to get Configuration with getConfiguration. On first call, it runs over 60-100 Seconds.
After the first call, its runs fast, but the first call freeze the Application for 60-100 Secounds.

Can you help me to correct the bug?
Feb 25, 2013 at 5:58 PM
Edited Feb 27, 2013 at 6:34 PM
My Code is:
             WatTmdb.V3.Tmdb api = new Tmdb("key", "de");
             TmdbConfiguration config = api.GetConfiguration();
            string baseUrl = config.images.base_url;

                int page = 1;
                int i = 0;
                while (i == 0)
                    var result = api.SearchMovie(search, page);
                    if (result != null)
Can i create the object "api" at the beginning in a thread? Is this possible? So the 5-10 seconds are not so bad, because nobody will notice it
Mar 18, 2013 at 1:33 PM
I'm really not sure what to suggest at this point. I'd thought perhaps the problem might be inclusion of the language causing problems, but testing that myself gives fast response regardless.

How does it go just calling into the API from IE or Chrome?

Mar 18, 2013 at 2:26 PM
When i call the API in IE or FF, i get a Response in less than 1 sec, so i thougt :)

I will test it with another Internet Connection. Perhaps this is the Problem. I will report my results.
Mar 22, 2013 at 3:37 PM
I have tried it this morning and guess what, in just 1 second the response was there.

Thanks watway for your help,
but now i have to look at my network at home for searching the problem.