I believe Sterling is looking for an end-user solution. The problem with
running telnet on port 80 is that it is the well-known http port. You can
telnet to http and vice versa, but it would not be much fun.
I'm working on a pub/sub service that has an http service endpoint. I'll
provide a windows app client that will give you spots on telnet using
localhost (127.0.0.1).
It should be ready in the next week or so.
For those techies out there, I'm running a RabbitMQ instance on a beefy VPS
that my AB5K cluster is running on.
Distributed pub/sub is where DX spots should be going; telnet is a fact of
history.
73,
Gerry W1VE
dxc.w1ve.com
On Wed, May 22, 2019, 8:30 AM rjairam@gmail.com <rjairam@gmail.com> wrote:
> https://www.dxcluster.co.uk/api
>
> A lot of APIs in there.
>
> 73
> Ria, N2RJ
>
> On Tue, 21 May 2019 at 19:44, Sterling Mann <kawfey@gmail.com> wrote:
> >
> > In a nutshell, I'm on a network that blocks non-standard ports including
> > telnet, making it a pain to use DX cluster since I can only access web
> > clients like DXsummit.fi. Before I go down the route of begging for
> > telnet/non standard port access, is anyone aware of any development of
> HTTP
> > cluster streams? Or maybe a telnet cluster on port 80?
> >
> > I lack networking expertise so go easy on me.
> >
> > Thanks,
> > Sterling N0SSC
> > _______________________________________________
> > CQ-Contest mailing list
> > CQ-Contest@contesting.com
> > http://lists.contesting.com/mailman/listinfo/cq-contest
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|