[DGD] The battle of the protocols (was: A small toy)

[Raymond Jennings]

On Fri, Feb 10, 2017 at 3:10 PM, <bart at wotf.org> wrote:

> On Fri, 10 Feb 2017 14:04:38 -0800, Raymond Jennings wrote
> <snip>
> > 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.
>
> Except for the technically inclined who had an opportunity to investigate,
> most people don't know and generally don't have to know about such things.
>
> Anyway, browsers only using a few standard protocols makes it a lot easier
> to
> keep browser based apps and sites working in an otherwise strictly
> controlled
> network which doesn't allow direct internet access (such as in many
> corporate
> environments).
>

I beg your pardon, but TCP is a very standard protocol...just at a lower
layer than HTTP.

I'm only saying that a TCP/UDP based api would be useful.  I'm NOT saying
that security policies should allow SUCCESS at using the api though...

The hoops one must jump through to get a plain old stream connection is
very annoying.  Java or flash applets usually wound up having to be written
and I'd much rather just use javascript.  Javascript is more transparent
anyway and I'd rahter run a script than load an unknown black box with
flash or java in it.

>
> Bart.
>
> >
> > </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
> > ____________________________________________
> > https://mail.dworkin.nl/mailman/listinfo/dgd
>
>
> --
> http://www.flickr.com/photos/mrobjective/
> http://www.om-d.org/
>
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd
>