Tim Watson

Guys, I'm getting a bit stuck with this. I do **not** want to specify the exact input type for my gen server, as this means that it can **only deal...

> So @edsko my question is, taking the following, which compiles (therefore it must work!) Urgh - I take that back, I just hadn't reconfigured recently enough. ``` src/Control/Distributed/Platform/GenProcess.hs:53:47: Ambiguous...

Well.... >  @hyperthunk I have been hitting similar issues trying to improve GenServer in different ways: Maybe I'm wrong but I suspect this will require either some clever redesign on...

> @hyperthunk Just as a quick side note re: "..., but with our knowledge (or lack) of it". Change that 'our' to a 'my' as I don't have a lot...

> @hyperthunk Ok, the pull request is in. I will not have time for this until the weekend. That's absolutely fine, I'm doing this in my spare time too and...

@edsko totally understood - we're all doing this on the side. I'll liaise with @rodlogic and we might potentially contribute some stuff to distributed-process a bit later on, though for...

> There is more refinements needed but the next todo there seems to figure out how to thread the server state through > the handlers/callbacks. The approach I am pursuing...

@rodlogic - first of all, thank you so much for your ongoing contributions; you've really pushed this forward and I think you've pretty much cracked the gen server API for...

@rodlogic yes I think it was the right place to deal with that issue. So regarding the API, I've just pushed a [new branch](https://github.com/hyperthunk/distributed-process-platform/tree/gen-process) which is worth a look. What...

So it is safe for us to kill this `ProcessId` from _our_ point of view, because we're deleting the child spec (and therefore won't require this "re-starter process" to continue...