Is there any rollover/archive option of the XML cache? For some of our customers this file is growing bigger and bigger, and we are wondering if this can be set to rotate/rollover like log4net or some appender.
We also experience problems with custom fields in orders, after finalizing. Because of the cache, it is not always possible to show the new/edited fields.
If the cache can be set to 4 hour intervals, the updating would be much faster.
You could register your own version of the IOrderRepository which is the one that does the caching. You would have to inherit from our own implementation in the TeaCommerce.Api.Persistence API. I have no example of this as its a quite new "feature" request :)
Else you would need to delete orders - but that is properly not an option?
First of all, thanks for the feedback; I will look into a custom order repository for future reference.
Secondly, how does the default XML perform in case of high traffic sites? We are currently migrating a customer from a legacy PHP shop to TeaCommerce. Approx. 1000 to 2000 orders are places each month.
Is it necessary to build a custom repo, or does the standard one suffice?
We havent done extreme testing of the order cache. So I cant give you a specific answer. I know that gordonramsey.co.uk runs a lot of orders per day. So I think the performance is good. But if you would like to help test the performance I would be really happy.
Finalized Order XML Cache
Hi all,
Is there any rollover/archive option of the XML cache?
For some of our customers this file is growing bigger and bigger, and we are wondering if this can be set to rotate/rollover like log4net or some appender.
We also experience problems with custom fields in orders, after finalizing. Because of the cache, it is not always possible to show the new/edited fields.
If the cache can be set to 4 hour intervals, the updating would be much faster.
Kind regards,
Peter Rombouts
Hi Peter
You could register your own version of the IOrderRepository which is the one that does the caching. You would have to inherit from our own implementation in the TeaCommerce.Api.Persistence API. I have no example of this as its a quite new "feature" request :)
Else you would need to delete orders - but that is properly not an option?
Kind regards
Anders
Hi Anders,
First of all, thanks for the feedback; I will look into a custom order repository for future reference.
Secondly, how does the default XML perform in case of high traffic sites?
We are currently migrating a customer from a legacy PHP shop to TeaCommerce.
Approx. 1000 to 2000 orders are places each month.
Is it necessary to build a custom repo, or does the standard one suffice?
Kind regards,
Peter Rombouts
We havent done extreme testing of the order cache. So I cant give you a specific answer. I know that gordonramsey.co.uk runs a lot of orders per day. So I think the performance is good. But if you would like to help test the performance I would be really happy.
Hi Anders,
We will keep you posted on our testing progress!
Kind regards,
Peter Rombouts
is working on a reply...