I've polished up my utility I'm calling HTTPmodem.
It can use SFTP, Jirafeau, URL Rewrite (fixed httpd served location URL+File Name), or File Copy (copy file to httpd served location).
Should note this will probably only help the Windows BBS Sysops,
(written in .net 3.5) but I will publish source on my site if somebody wishes to port it.
I've polished up my utility I'm calling HTTPmodem. It's a file transfer protocol for BBSes. It will allow a Sysop to upload, copy, build HTTP(S) URLs for users to download files from their BBS. You will need a web server of some sort to serve the files, and a 32-bit DOOR32.SYS BBS system.
Fully tested with Mystic and with my custom coded system. Should work with Synchronet as it does the same calls for FTPs.
For options like sftp or copy, is there a time limit for the lifespan of the file? Or are destination files overwritten when a new version of the same filename is requested (eg: an updated network infopack)?
I'm not sure about porting from .Net but it might be possible to
replicate the functionality through shell scripting.
Does it know how to generate the URLs from the Synchronet filebase?
Seems like it might have to know how to access the Synchronet filebase
to know how to generate the FTP link. As far as I know, Synchronet currently does not provide external APIs for accessing its filebase (at least for JavaScript)..
If you wanted to use the Synchronet filebase (and it's publicly accessible) you can set the URL in the INI to be say "ftp://bbs.domain.com/" and when choosing the FTP at download it will spit out "ftp://bbs.domain.com/<filename>". Now if your files are in say "ftp://bbs.domain.com/<filearea>/<filename>" I will try to add a flag to take the subdirectory/file area and append it as well.
This would use the 'upload option' in the INI as 2 'static url rewrite'. I don't use Synchronet, but is the above what your thinking?
Not sure.. It sounds like that would require manually adding an FTP URL for every file available for download on the BBS in order to work with this transfer protocol?
I've polished up my utility I'm calling HTTPmodem. It's a file transfer protocol for BBSes. It will allow a Sysop to upload, copy, build HTTP(S) URLs for users to download files from their BBS. You will need a web server of some sort to serve the files, and a 32-bit DOOR32.SYS BBS system.
Mystic already allows users to download their "batch queue" when logged into the telnet BBS via FTP/web browser. It can optionally generate an expiring dynamic URL for that particular user where they can connect and browse/download the files they've queued with an FTP client or web browser.
First question, when the NS option is used it uses theme lines 179 and 180. I modified those lines so it won't clear the screen, it just XY to
a specific area and prints the broadcast text. Is there a way to not 'restore' the screen after message is received? It seems to repaint the previous screen (erasing the message). I currently use a few |DE to
(which will clear it anyway)?
refers to ProgParams. I cant seem to pass the string into the program
when using mystic -Uxxx -Pxxx -Xmenucmd "0;Testing". I'm sure I am doing this incorrectly.
Neat, can you point me in the direction to explore this? I would love to read more and try some things out.
Not really, because those messages can be shown at any time which would distort the user's screen if Mystic wasn't able to restore the screen afterwards.
It looks like you are not giving it a menu command to run and you need to enclose the entire option in quotations if there are spaces. I'm not in
a place where I can try it or reference the command line syntax but it should be something close to:
I have it on the "todo" list to add a "broadcast" option to Nodespy so
you can send messages from the command line: "nodespy.exe broadcast This is a message!" Although I may add this to "mystic.exe" instead.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 102 |
Nodes: | 16 (0 / 16) |
Uptime: | 10:55:42 |
Calls: | 5,860 |
Files: | 8,496 |
D/L today: |
35 files (26,679K bytes) |
Messages: | 344,374 |