[DGD] A small toy

[Raymond Jennings]

When are browsers going to stop being shy about direct vanilla TCP
connections?

If it's a security issue, just pop up a dialog and ASK for permission, or
ask the administrative policy shebangs.

We live in the 21st century, and people know by now about ports and
addresses.  It's time for browsers to stop treating users like morons.

</rant>

On Fri, Feb 10, 2017 at 12:40 PM, Neil McBride <neil at dogl.net> wrote:

> I once spent a lot of time implementing http and websockets in DGD back
> when websockets was in early development and only available in a couple of
> browsers. Haven't looked at it for a long time and always thought it would
> be better to have something else handle the protocols you're using nodejs
> for.
>
> Any chance on releasing the code? I'd love to see how how tied it all
> together.
>
> Neil
>
>
> On 10/02/2017 11:38 PM, bart at wotf.org wrote:
>
>> Service runs on DGD, but http and websockets are handled by a small
>> request
>> router running on nodejs. The nodejs code is less then 100 lines, the lpc
>> code
>> is a lot more (around 200k for the entire system). The request router and
>> lpc
>> backend use a json based api to talk to eachother.
>>
>> http://fortune.wotf.org/
>>
>> Ah yes, its still quite experimental, more of a 'hey this works' thing,
>> but
>> thought you might like it.
>>
>> Bart.
>> --
>> http://www.flickr.com/photos/mrobjective/
>> http://www.om-d.org/
>>
>> ____________________________________________
>> https://mail.dworkin.nl/mailman/listinfo/dgd
>>
>
>
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd