tired of it!

Hello, Denis! Thu 18-Dec-97 01:47, Denis Parinov (2:5030/529.13) wrote a letter to Paul Falcon: DP> there is a problem. In theory, we need to make a tosser for PKT. Otherwise DP> will have to be rewritten later. On the other hand, the editor for DP> PKT view, no. All that remains is to do it according to the existing standard. The tosser is the intermediate link between the PCT and the editor. He scatters letters from pkt according to the database. The format of the database should also be understandable to the editor. There is something on the pussy at least four database formats. The simplest one is fidomsg - each aria in its own directory, each letter is a separate file in this directory. Tosser is doing and the reverse process - exports fresh letters (written by you) from the database to pct. Therefore, you need to write both the tosser and the editor together. You can, of course, store letters to PKT and train the editor in this particular format, but this is unsportsmanlike - letters from one aria will be lying around in different packages, whereas in the database they are all lie in the required aria. With best wishes, Vladimir.

Hello, Denis! Thu 25-Dec-97 03:32, Denis Parinov (2:5030/529.13) wrote a letter to Vladimir Larkov: VL>> Therefore, you need to write both tosser and editor together. You can, of course, store VL>> letters in PKT and train the editor in this particular format, but VL>> this is unsporting - letters from one aria will lie in different ones VL>> packages, whereas in the database they are all in the required aria. DP> In SpbZxNet everything is a little different from in Fido ;) I'm aware ;) DP> Messages in the echo are written in the editor and then uploaded DP> to any BBS, and from the BBS they come to the HUB which is everything DP> messages are glued together by echoes (one echo - one file) and output DP> back to BBS. From there they download points, etc. So I say that a tosser would be nice for human work. And don't the hub will “glue”. Look - we have several pkt from, say, a point. I went tossing. (In this example you are a node and it is assumed that there is already a tosser). B These pkt'shki say 30 letters in 6 arias. Five each. What does the tosser do: takes the first letter and looks at which aria. Let's say in SALE. Tosser is watching The level of this point for recording in this aria. Let's say the level for aria is atyou have 9000, and the point has 10000, therefore the point has the right to write to this echo. We begin to process the letter. Let's see who is subscribed to this aria. Let's say three your point and one hub. We throw this letter into some temp pkts for everyone four (and to your database, if you read it yourself). Let's take the trail. letter. Let's say it's in GENERAL. Again, look at the point level. 8000, and you have 10000. Therefore, the point has no right to write to this echo. The letter is postponed to BAD aria with the corresponding postscript. (In the future, if you raise this point level, accordingly allowing writing to this aria, a letter from a bad aria can be will re-suck. And then it will fall where it needs to). The next letter to the CODE aria, You have two subscribers to it. This means we assign it only to pkts for these two. All letters are processed this way. At the end we have personal pkt for each of your links plus the latest letters in your database (in those echoes which you yourself read). Bundles for the mailer are being created. Tossing is over. (was If there was an archiver - at the end there would be a package of pkt's). PS: bundle is a file with full paths and file names. During the session, the soaper scans bundles and gives files to links according to what is written in the bundles. After After this, the transferred files are either erased or reset. Depending on the first character at the beginning of the line in the bundle.ZZY: FTN technology is quite well thought out - is it worth reinventing your own wheel? With best wishes, Vladimir.

Hello, Denis! Tue 30-Dec-97 00:30, Denis Parinov (2:5030/529.13) wrote a letter to Vladimir Larkov: DP> The only thing that confuses me is the size of the floppy disk, whether the node will fit so much information DP> because for now the screw on the Spectrum is the exception rather than the rule :( The most common option IMHO is Scorp + 2 flops. In isdos the disk is 800 kilos. We keep the mailer/tosser in the frame (208 kg is enough IMHO). Disk "A" is your base. If not let it grow half a meter, then 300 kilos are left for reception/tempo. Disk "B" - outbound on links. Divide 800 kilos by the number of links - how much is there on average? points on the node? In addition, after sending the link, the space occupied package, released. With best wishes, Vladimir.

02-01-98, at 14:05:00, Vladimir Larkov wrote to Denis Parinov, on the topic: "tired of it!"... Big Hello, Vladimir! VL> Hello, Denis! DP>> The only thing that confuses me is the size of the floppy disk, whether the node will fit so much information DP>> because for now the screw on the Spectrum is the exception rather than the rule :( VL> The most common option IMHO is Scorp + 2 flops. In isdos disk 800 VL> kilo. I'll give you isdos! And don't even think about it! TR-Dosnykh 640kb is enough. VL> We keep the mailer/tosser in the frame (208 kg is enough IMHO). Disk "A" is your base. VL> If ^^^^^^^^^^^^^^^^^^ What if I have a 48 with a floppy drive? VL> do not let it grow beyond half a meter, then 300 kilos remain for reception/tempo. VL> Disk "B" - outbound for links. Divide 800 kilos by the number of links - how many are there VL> average points per node? In addition, after sending the link there is a place 50 points. VL> occupied by the package is freed. Don’t forget, the tosser is written only for TR-Dos, and under its is-dos no one is going to rewrite it. In addition, you still need a mailer. And it’s not even under tr-dos... :( VL> With best wishes, Vladimir.Sincerely yours, Arny Sinen from -=VS prog=- -+- SMM version 1.05