Hacker News Reader

So does this mean I can shove SQLite databases into the file structure, abstract away an entire SQLite engine into a single header that you are forced to use, and declare that IPC? And you know, since we _are_ already hiding databases within the file structure, why not use it to also unify configuration and installation files too? What could go wrong?

View on HN

I’m having trouble following what you mean.

Yes, you can certainly send a whole SQLite database using any binary communication protocol as a way to exchange data today. You can even compress it before if you feel like it.

It will not make for a good ipc format because, well, it’s not designed to be one but it would most definitely work.

What’s your point?

My point is, what's stopping me from creating yet another IPC standard?

Nothing. It might not see adoption, but you can create as many IPC standards as you desire.

There is this one somewhat widely deployed niche system that uses sqlite databases as RPC serialization format. The original idea behind that was limited virtual address space of the CE-based embedded devices, but the design got stuck.

Could you name it?

Naming the system would be useful context to add to this point.

Reply on news.ycombinator.com