Overarching Goal:
The overarchiving goal of 'Scientists' is to allow for debugging while comparing against the 'official' PCFS implementations. Basically being able to serve files to a cat-dev unit, while also proxying the cat-dev requests to a system running a real Cafe SDK setup, and diffing the two live in real time. Not only that, but ideally you should be able to diff against multiple Cafe SDK implementations at the same time.
The goal of this came out of the previous unstable booting experience from pre #21 . Turns out that #21 just had quite a few issues that needed to be fixed, leading to what #21 became which was an absolutely full from the ground up rewrite of the TCP servers.
Most of the "core struct"'s should already support this. TCP Server's don't really need to do a ton here as the scientist interface will mostly just augment the server with a TCP Client connection at the same time. The TCP Client interface already supports interacting with many upstreams at the same time without calling many different functions. You can also fetch all the requests from a previously requested RequestID. As well as broadcasting to many upstreams at once.
Of course getting these core struct's to actually work all together, and show a very nice diffing interface... is.... gonna be quite a bit of work. So this is gonna be quite a huge chunk of work.
There's not really a timeline for these features, we may need them someday, ideally we solve it before then but,,,, i've got way too many things so i can't promise i'll do that.
Overarching Goal:
The overarchiving goal of 'Scientists' is to allow for debugging while comparing against the 'official' PCFS implementations. Basically being able to serve files to a cat-dev unit, while also proxying the cat-dev requests to a system running a real Cafe SDK setup, and diffing the two live in real time. Not only that, but ideally you should be able to diff against multiple Cafe SDK implementations at the same time.
The goal of this came out of the previous unstable booting experience from pre #21 . Turns out that #21 just had quite a few issues that needed to be fixed, leading to what #21 became which was an absolutely full from the ground up rewrite of the TCP servers.
Most of the "core struct"'s should already support this. TCP Server's don't really need to do a ton here as the scientist interface will mostly just augment the server with a TCP Client connection at the same time. The TCP Client interface already supports interacting with many upstreams at the same time without calling many different functions. You can also fetch all the requests from a previously requested RequestID. As well as broadcasting to many upstreams at once.
Of course getting these core struct's to actually work all together, and show a very nice diffing interface... is.... gonna be quite a bit of work. So this is gonna be quite a huge chunk of work.
There's not really a timeline for these features, we may need them someday, ideally we solve it before then but,,,, i've got way too many things so i can't promise i'll do that.