First of all, I’m glad that the days of digging into POCO library and locating the code segment which removes elements upon exipration didn’t go wasted. I managed to get the caching expiration mechasmin done without any error despite having run into several problems before. For example, the actual code implements class template which is nested. I was initially quite confused by this but I managed to understand it and implement it at the end. The other challenge was constructing the object inside the class defined and the order of initialization. This had already been discussed in the previous blog post but without the order of initialization. It turns out that the order of initialization is not based on the order you put it in the initializer list but the order of declaring it in the class. For instance,
Class X:
A a;
B b;
X(): b(param), a(param){
}
In this case, object “a” will be initialized first since it is declared first.
Also, starting from now onwards, I will be working with one of my colleague on front-end integration. This project will be using admin-on-rest as the front-end side which makes a lot of things easier as it has almost done everything for you. However, integrating the back-end with this is more painful than what I thought, as a lot of things you can’t alter from the front-end but you have to do it from the back-end. For example, you can’t control the type of request sent by admin-on-rest, but your back-end has to give the corresponding response to the request that has been fixed. Another problem is admin-on-rest doesn’t send parameters through query string (http://127.0.0.1/blog?parameter=xxx) but instead in the request body in the JSON format. These are the problems that I have encountered so far, but I expect more problems to come in the next few weeks.
0 Comments