Harold Hartley wrote:
> > It is a configurable server designed for limited web pages from the
> > internet to include callbook servers, dxcluster, or any other service
you
> > wish to provide and will interface to http on the 'net.
> >
> > According to the QST article (written by John Hansen, W2FS) the server
> > uses UI frames exclusively, so essentially it runs in broadcast mode all
> > the time. So what I gather is that depending on the request and baud
rate
> > of the requesting station, different information replies to the
requester
> > are sent (it is up to the requesting stationor server to determine
> > efficiency of his/her connection - baud rate, etc.).
> >
then Bob Meyer wrote:
> Okay it's a file server using ax25 in disconnected mode. Kind of an aprs
> style file server.
>
> Wouldn't this work a lot better?
> http://gw.ko6ri.ampr.org/bbs/cgi-bin/callbook.cgi?kb6fst
I think both these miss the REAL point of ham web - that it's a broadcast
protocol. It's conceptually similar to that used by the pacsats. It's real
benefit, and one that makes it very suitable to web serving over packet
radio, is that ANY file can be transferred to MANY stations simultaneously.
IIRC it doesnt have the "hole request" capability of the pacsat protocol,
but sends the file(s) repeatedly. Hence bulletins, web pages, mail, or
anything else that can be bundled up as a file, transferred, then unbundled
and processed can make use of it. The existing version already has some
hooks into existing software packages. Web is just one application for it.
It's also worth pointing out that the specifications are documented, so a
Linux version could be implemented.
73
Steve
