GSoC project discussions

[Prasun Kumar]

Regarding the feedback from the AqBanking project...

> That's why I was contemplating providing some service like libofxhome
> where you can query a bank data provider. Then you would only need to
> update the data in one place (on the server).
>

Can someone point me to 'libofxhome' service which is mentioned as I don't
understand the type of service discussed here? Is it a web-based service?

>From my point of view it would be best if we could use your database as
> a stand-in for e.g. ktoblzcheck (which we formerly used to check bank
> German account numbers); as a separate library which can be used by
> applications or other libraries (like AqBanking).
>
How is it different from the current approach of the project? And what does
'stand-in' means in this context?

Thanks,
Prasun


On Sat, 9 May 2020 at 19:06, Prasun Kumar <prasun.code at gmail.com> wrote:

> Hi everyone,
> As mentioned in the project proposal, one of the major tasks is to replace
> the text bankdata files with an SQLite database. Currently, KtoBlzCheck
> comes with one data file which is valid at the time of release. Then during
> building, a file valid at the current date is downloaded from the bank and
> converted into a file suitable for the library. *So, when migrating to an
> SQLite DB, how should this DB file be distributed and updated?*
> One possible way might be to provide the DB at the time of release and at
> build time, download the raw file from the bank and update the DB with this
> file. But in this case, wouldn't it be more efficient to create a new DB
> file based on the new data and replace the older DB rather than searching
> each bank and updating it from the file? *Specifically, I wanted to know
> if there is a reason to store the older bankdata files and their data.*
>
> Thank you,
> Prasun
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-finance-apps/attachments/20200509/e8102eaa/attachment.htm>