#indicowalker

I've been slowly converting the memory model to be a lot more efficient (still to be seen if that works), but testing, and getting a set of tests that work has wasted a lot more time than I should have! It has me wondering, actually, if this isn't the right way to do things - or perhaps I should be moving back to something else not involving Rx programming. On the other hand, having everything hanging off the ctor is just so clean!

The main problem seems to be time travel. Rx has some nice things like a test scheduler which helps a lot with testing in Rx and time. You can put in a delay, and then use the scheduler to release the delay when you want. Sweet.

The problem comes when you start involving multiple threads and SemaphoreSlim's... at some point it seems like the test scheduler just stops working [I didn't try to debug it itself]. Rather, I switched all the tests to use the normal schedulers and found other ways to record what was going on, and make sure the testing was being done right.

I've not seen much about this on stack overflow.

The old setup worked just fantastic when having to deal with small ATLAS meetings. Even longer meetings like an ATLAS week seemed to work ok.

But CHEP would cause lots of faults, and crashes. Mostly out of memory errors.

Also, virtualization was turned on automatically for these long lists. However, the way my code worked was once the meeting was loaded every single talk for a single day would be rendered to an image and displayed. Regardless of it being displayed or not.

So this means it is a change. In part, this is about playing better with Rx than I was in the first time. So had I been smarter, perhaps this re-write and re-factoring could have been avoided.

When the meeting is opened, and by default all talks are to be downloaded, then fire off downloads. The files are placed in the cache, but nothing more is done.

When a PDF Page guy is in view, it subscribes to an observable, which causes the PDF file to be loaded from the cache, turned into a PDF file, and rendered. Once loaded, the PDF file is held onto as long as anyone is interested in it. I’m not 100% confident of this logic, we will have to check it when all is done. But everything should be released when it goes out of view.

All information needed to display the images from a pre-rendered talk (e.g. one that has been looked at before) should be cached, so the PDF file is not rendered. This means when you load up a meeting and see the grid of slides, if this isn’t the first time, no PDF files should be loaded, and no rendering should run.

First thing was to move it to use the new universal projects and PCL's. They have advanced significantly since I first wrote this code. In particular, it is now time to move to Windows.Net.Http, which involves a lot of changes. In particular, how the credentials are used.

The basic things are the same (see previous posts on CERNSSO). In particular, the fact that a Windows App has only the local cert store. What is nice, now, is that also exists on Windows Phone - so with 8.1 they are identical finally. It wasn't possible to do anything with certificate stores on WP previously.

But this makes me wonder. Why can't I add the cert and make the web request, allow redirects, and let the underlying system (which mimics a browser) just work? That would be a lot simpler than doing what I'm currently doing. Testing that is going to require some effort. :-)

Found some example code on accessing certificates and associating them with a request in the windows runtime here.