Talk:Distributed programming
I used IRC for the AutoHotkey entry. Is that allowed? BR
- Whether it's allowed or not I think it would be better if it were on its own page (Distributed program/AutoHotkey) and that page simply had a link on this page. --Mwn3d 15:50, 9 September 2009 (UTC)
- Done. --glennj 16:37, 9 September 2009 (UTC)
- Part of the problem is that he included the source of a library the program depends on. Talked to him on IRC, suggested he use Template:libheader. --Michael Mol 16:55, 9 September 2009 (UTC)
- I moved WinSock2.ahk to WinSock2.ahk, is it short enough now to put back in the main page? BR
- 7000 bytes is still pretty big. I wonder if maybe the Python examples could be broken out too. We don't need more problems with loading large pages. It'd be best to get the especially long examples as they come up rather than try to fix the problem after the fact. --Mwn3d 17:06, 9 September 2009 (UTC)
- I moved WinSock2.ahk to WinSock2.ahk, is it short enough now to put back in the main page? BR
Insufficiently general?
A lot of the examples are slapped with this label. Now what is a "sufficient" one? One that can pass arbitrary sized data blocks? One that can also mark native/network endianess? One that can annotate the data's structure? Or even with extended attributes/metadata? Can we just send XML along with schema in utf-8 which must be fully strict, hence very likely to be correct but going to be horribly slow? Maybe this task needs some review. --Ledrug 03:55, 18 June 2011 (UTC)
Hi. I wrote the original task. My intent was that it should show the use of distributed programming as opposed to simply being able to use the network — we have other tasks for that. The facilities used to accomplish the task should be suitable for performing a complex task distributed across several machines. Or something like that. Trying to be sufficiently specific about sufficiently general, I'd say it should be a protocol/library which at least supports a reasonable set of common data structures, and preferably has a notion of messages/RPCs, such that the author of the example does not have to invent a protocol, especially not a data serialization scheme, as opposed to just spreading their program across the network.
I've also expanded the task description a bit. I tried to avoid wording it exclusively. —Kevin Reid 04:20, 18 June 2011 (UTC)