Hi!

I understand that people in China may have another perspective on this, so I take no offense. In any case, I hope your home will never be bombed as was mine.

As for the refund, I'd love to issue it for you, but your order was placed more than 6 months ago, so a refund is not possible according to our payment processing company policy.

Hi!

There are two ways to do it:

1. Move the kfx file to the content folder of the Kindle reader and restart the app. By default, it is "C:\Users\%Username%\Documents\My Kindle Content". This directory can be changed in the Kindle app settings (Tools > Options > Content).

2. If you associate kfx files with the Kindle app, simply opening the file will also work. To do this, right-click the kfx file, select "Properties" from the context menu. Then, in the "Open with" field, pick the Kindle executable (it's usually located at "C:\Users\%Username%\AppData\Local\Amazon\Kindle\application").

Please let me know if you have any further questions.

Здравствуйте, Игорь!

Книга не издавалась ранее в печатном виде. Увы, но пока что никаких новостей по печатной версии нет.

Hi!

Thanks for the bug report! I've just fixed this issue. Please reload the page to get the update.

Hi!

The database connection can be lazy initialized as well. The most common use in regards to databases would probably be a caching proxy. Suppose your server hosts a content management system that loads content from a slow remote database. The server has a fast local memory cache that can store already loaded pieces of content. The proxy could implement this behavior, fetching content from the fast memory cache if it's there and defaulting to the slow database if not.

In this scenario, when do you establish the database connection?

— You can do it right in the Proxy constructor. This will slow down the initialization phase, but the database connection will be ready by the time the proxy has to call the database.

— Or you can go with the lazy loading approach, establishing the database connection only if the proxy needs to call the database (this may never happen if the cache is full). The initialization of the proxy will be much faster as you don't wait for the database, but the first request to the database will be slower, as you'll need to establish the connection first. However, if all the required content is already in the memory cache, the proxy might never need to call the database, and thus that slow down on the first request is not critical.

Hi Devang!

Can you please clarify what links do you mean?

Hi!

Thanks a lot for taking the time to report this issue. I'll address it soon and upload the fix with the next update. Thanks again!