Then I wonder and figure the re-routine can scale.
Here for the re-routine, the industry factory pattern,
and the commands in the protocols in the templates,
and the memory module, with the algorithm interface,
in the high-performance computer resource, it is here
that this simple kind of "writing Internet software"
makes pretty rapidly for adding resources.
Here the design is basically of a file I/O abstraction,
that the computer reads data files with mmap to get
their handlers, what results that for I/O map the channels
result transferring the channels in I/O for what results,
in mostly the allocated resource requirements generally,
and for the protocol and algorithm, it results then that
the industry factory pattern and making for interfaces,
then also here the I/O routine as what results that this
is an implementation, of a network server, mostly is making
for that the re-routine, results very neatly a model of
parallel cooperation.
I think computers still have file systems and file I/O but
in abstraction just because PAGE_SIZE is still relevant for
the network besides or I/O, if eventually, here is that the
value types are in the commands and so on, it is besides
that in terms of the resources so defined it still is in a filesystem
convention that a remote and unreliable view of it suffices.
Here then the source code also being "this is only 20-50k",
lines of code, with basically an entire otherwise library stack
of the runtime itself, only the network and file abstraction,
this makes for also that modularity results. (Factory Industry
Pattern Modules.)
For a network server, here, that, mostly it is high performance
in the sense that this is about the most direct handle on the channels
and here mostly for the text layer in the I/O order, or protocol layer,
here is that basically encryption and compression usually in the layer,
there is besides a usual concern where encryption and compression
are left out, there is that text in the layer itself is commands.
Then, those being constants under the resources for the protocol,
it's what results usual protocols like NNTP and HTTP and other protocols
with usually one server and many clients, here is for that these protocols
are defined in these modules, mostly there NNTP and IMAP, ..., HTTP.
These are here defined "all Java" or "Pure Java", i.e. let's be clear that
in terms of the reference abstraction layer, I think computers still use
the non-blocking I/O and filesystems and network to RAM, so that as
the I/O is implemented in those it actually has those besides instead for
example defaulting to byte-per-channel or character I/O. I.e. the usual
semantics for servicing the I/O in the accepter routine and what makes
for that the platform also provides a reference encryption implementation,
if not so relevant for the block encoder chain, besides that for example
compression has a default implementation, here the I/O model is as simply
in store for handles, channels, ..., that it results that data especially delivered
from a constant store can anyways be mostly compressed and encrypted
already or predigested to serve, here that it's the convention, here is for
resulting that these client-server protocols, with usually reads > postings
then here besides "retention", basically here is for what it is.
With the re-routine and the protocol layer besides, having written the
routines in the re-routine, what there is to write here is this industry
factory, or a module framework, implementing the re-routines, as they're
built from the linear description a routine, makes for as the routine progresses
that it's "in the language" and that more than less in the terms, it makes for
implementing the case of logic for values, in the logic's flow-of-control's terms.
Then, there is that actually running the software is different than just
writing it, here in the sense that as a server runtime, it is to be made a
thing, by giving it a name, and giving it an authority, to exist on the Internet.
There is basically that for BGP and NAT and so on, and, mobile fabric networks,
IP and TCP/IP, of course IPv4 and IPv6 are the coarse fabric main space, with
respect to what are CIDR and 24 bits rule and what makes for TCP/IP, here
entirely the course is using the TCP/IP stack and Java's TCP/IP stack, with
respect to that TCP/IP is so provided or in terms of process what results
ports mostly and connection models where it is exactly the TCP after the IP,
the Transport Control Protocol and Internet Protocol, have here both this
socket and datagram connection orientation, or stateful and stateless or
here that in terms of routing it's defined in addresses, under that names
and routing define sources, routes, destinations, ..., that routine numeric
IP addresses result in the usual sense of the network being behind an IP
and including IPv4 network fabric with respect to local routers.
I.e., here to include a service framework is "here besides the routine, let's
make it clear that in terms of being a durable resource, there needs to be
some lockbox filled with its sustenance that in some locked or constant
terms results that for the duration of its outlay, say five years, it is held
up, then, it will be so again, or, let down to result the carry-over that it
invested to archive itself, I won't have to care or do anything until then".
About the service activation and the idea that, for a port, the routine itself
needs only run under load, i.e. there is effectively little traffic on the old archives,
and usually only the some other archive needs any traffic. Here the point is
that for the Java routine there is the system port that was accepted for the
request, that inetd or the systemd or means the network service was accessed,
made for that much as for HTTP the protocol is client-server also for IP the
protocol is client-server, while the TCP is packets. This is a general idea for
system integration while here mostly the routine is that being a detail:
the filesystem or network resource that results that the re-routines basically
make very large CPU scaling.
Then, it is basically containerized this sense of "at some domain name, there
is a service, it's HTTP and NNTP and IMAP besides, what cares the world".
I.e. being built on connection oriented protocols like the socket layer,
HTTP(S) and NNTP(S) and IMAP(S) or with the TLS orientation to certificates,
it's more than less sensible that most users have no idea of installing some
NNTP browser or pointing their email to IMAP so that the email browser
browses the newsgroups and for postings, here this is mostly only talk
about implementing NNTP then IMAP and HTTP that happens to look like that,
besides for example SMTP or NNTP posting.
I.e., having "this IMAP server, happens to be this NNTP module", or
"this HTTP server, happens to be a real simple mailbox these groups",
makes for having partitions and retentions of those and that basically
NNTP messages in the protocol can be more or less the same content
in media, what otherwise is of a usual message type.
Then, the NNTP server-server routine is the progation of messages
besides "I shall hire ten great usenet retention accounts and gently
and politely draw them down and back-fill Usenet, these ten groups".
By then I would have to have made for retention in storage, such contents,
as have a reference value, then for besides making that independent in
reference value, just so that it suffices that it basically results "a usable
durable filesystem that happens you can browse it like usenet". I.e. as
the pieces to make the backfill are dug up, they get assigned reference numbers
of their time to make for what here is that in a grand schema of things,
they have a reference number in numerical order (and what's also the
server's "message-number" besides its "message-id") as noted above this
gets into the storage for retention of a file, while, most services for this
are instead for storage and serving, not necessarily or at all retention.
I.e., the point is that as the groups are retained from retention, there is an
approach what makes for an orderly archeology, as for what convention
some data arrives, here that this server-server routine is besides the usual
routine which is "here are new posts, propagate them", it's "please deliver
as of a retention scan, and I'll try not to repeat it, what results as orderly
as possible a proof or exercise of what we'll call afterward entire retention",
then will be for as of writing a file that "as of the date, from start to finish,
this site certified these messages as best-effort retention".
It seems then besides there is basically "here is some mbox file, serve it
like it was an NNTP group or an IMAP mailbox", ingestion, in terms of that
what is ingestion, is to result for the protocol that "for this protocol,
there is actually a normative filesystem representation that happens to
be pretty much also altogether definede by the protocol", the point is
that ingestion would result in command to remain in the protocol,
that a usual file type that "presents a usual abstraction, of a filesystem,
as from the contents of a file", here with the notion of "for all these
threaded discussions, here this system only cares some approach to
these ten particular newgroups that already have mostly their corpus
though it's not in perhaps their native mbox instead consulted from services".
Then, there's for storing and serving the files, and there is the usual
notion that moving the data, is to result, that really these file organizations
are not so large in terms of resources, being "less than gigabytes" or so,
still there's a notion that as a durable resource they're to be made
fungible here the networked file approach in the native filesystem,
then that with respect to it's a backing store, it's to make for that
the entire enterprise is more or less to made in terms of account,
that then as a facility on the network then a service in the network,
it's basically separated the facility and service, while still of course
that the service is basically defined by its corpus.
Then, to make that fungible in a world of account, while with an exit
strategy so that the operation isn't not abstract, is mostly about the
domain name, then that what results the networking, after trusted
network naming and connections for what result routing, and then
the port, in terms of that there are usual firewalls in ports though that
besides usually enough client ports are ephemeral, here the point is
that the protocols and their well-known ports, here it's usually enough
that the Internet doesn't concern itself so much protocols but with
respect to proxies, here that for example NNTP and IMAP don't have
so much anything so related that way after startTLS. For the world of
account, is basically to have for a domain name, an administrator, and,
an owner or representative. These are to establish authority for changes
and also accountability for usage.
Basically they're to be persons and there is a process to get to be an
administrator of DNS, most always there are services that a usual person
implementing the system might use, besides for example the numerical.
More relevant though to DNS is getting servers on the network, with respect
to listening ports and that they connect to clients what so discover them as
via DNS or configuration, here as above the usual notion that these are
standard services and run on well-known ports for inetd or systemd.
I.e. there is basically that running a server and dedicated networking,
and power and so on, and some notion of the limits of reliability, is then
as very much in other aspects of the organization of the system, i.e. its name,
while at the same time, the point that a module makes for that basically
the provision of a domain name or well-known or ephemeral host, is the
usual notion that static IP addresses are a limited resource and as about
the various networks in IPv4 and how they route traffic, is for that these
services have well-known sections in DNS for at least that the most usual
configuration is none.
For a usual global reliability and availability, is some notion basically that
each region and zone has a service available on the IP address, for that
"hostname" resolves to the IP addresses. As well, in reverse, for the IP
address and about the hostname, it should resolve reverse to hostname.
About certificates mostly for identification after mapping to port, or
multi-home Internet routing, here is the point that whether the domain
name administration is "epochal" or "regular", is that epochs are defined
by the ports behind the numbers and the domain name system as well,
where in terms of the registrar, the domain names are epochal to the
registrar, with respect to owners of domain names.
Then if DNS is a datagram or UDP service is for ICMP as for TCP/IP,
and also BGP and NAT and routing and what are local and remote
addresses, here is for not-so-much "implement DNS the protocol
also while you're at it", rather for what results that there is a durable
and long-standing and proper doorman, for some usenet.science.
Here then the notion seems to be whether the doorman basically
knows well-known services, is a multi-homing router, or otherwise
what is the point that it starts the lean runtime, with respect to that
it's a container and having enough sense of administration its operation
as contained. I.e. here given a port and a hostname and always running
makes for that as long as there is the low (preferable no) idle for services
running that have no clients, is here also for the cheapest doorman that
knows how to standup the client sentinel. (And put it back away.)
Probably the most awful thing in the cloud services is the cost for
data ingress and egress. What that means is that for example using
a facility that is bound by that as a cost instead of under some constant
cost, is basically why there is the approach that the containers needs a
handle to the files, and they're either local files or network files, here
with the some convention above in archival a shared consistent view
of all the files, or abstractly consistent, is for making that the doorman
can handle lots of starting and finishing connections, while it is out of
the way when usually it's client traffic and opening and closing connections,
and the usual abstraction is that the client sentinel is never off and doorman
does nothing, here is for attaching the one to some lower constant cost,
where for example any long-running cost is more than some low constant cost.
Then, this kind of service is often represented by nodes, in the usual sense
"here is an abstract container with you hope some native performance under
the hypervisor where it lives on the farm on its rack, it basically is moved the
image to wherever it's requested from and lives there, have fun, the meter is on".
I.e. that's just "this Jar has some config conventions and you can make the
container associate it and watchdog it with systemd for example and use the
cgroups while you're at it and make for tempfs quota and also the best network
file share, which you might be welcome to cache if you care just in the off-chance
that this file-mapping is free or constant cost as long as it doesn't egress the
network", is for here about the facilities that work, to get a copy of the system
what with respect to its usual operation is a piece of the Internet.
For the different reference modules (industry factories) in their patterns then
and under combined configuration "file + process + network + fare", is that
the fare of the service basically reflects a daily coin, in the sense that it
represents an annual or epochal fee, what results for the time there is
what is otherwise all defined the "file + process + network + name",
what results it perpetuates in operation more than less simply and automatically.
Then, the point though is to get it to where "I can go to this service, and
administer it more or less by paying an account, that it thus lives in its
budget and quota in its metered world".
That though is very involved with identity, that in terms of "I the account
as provided this sum make this sum paid with respect to an agreement",
is that authority to make agreements must make that it results that the
operation of the system, is entirely transparent, and defined in terms of
the roles and delegation, conventions in operation.
I.e., I personally don't want to administer a copy of usenet, but, it's here
pretty much sorted out that I can administer one once then that it's to
administer itself in the following, in terms of it having resources to allocate
and resources to disburse. Also if nobody's using it it should basically work
itself out to dial its lights down (while maintaining availability).
Then a point seems "maintain and administer the operation in effect,
what arrangement sees via delegation, that a card number and a phone
number and an email account and more than less a responsible entity,
is so indicated for example in cryptographic identity thus that the operation
of this system as a service, effectively operates itself out of a kitty,
what makes for administration and overhead, an entirely transparent
model of a miniature business the system as a service".
"... and a mailing address and mail service."
Then, for accounts and accounts, for example is the provision of the component
as simply an image in cloud algorithms, where basically as above here it's configured
that anybody with any cloud account could basically run it on their own terms,
there is for here sorting out "after this delegation to some business entity what
results a corporation in effect, the rest is business-in-a-box and more-than-less
what makes for its administration in state, is for how it basically limits and replicates
its service, in terms of its own assets here as what administered is abstractly
"durable forever mailboxes with private ownership if on public or managed resources".
A usual notion of a private email and usenet service offering and business-in-a-box,
here what I'm looking at is that besides archiving sci.math and copying out its content
under author line, is to make such an industry for example here that "once having
implemented an Internet service, an Internet service of them results Internet".
I.e. here the point is to make a corporation and a foundation in effect, what in terms
of then about the books and accounts, is about accounts for the business accounts
that reflect a persistent entity, then what results in terms of computing, networking,
and internetworking, with a regular notion of "let's never change this arrangement
but it's in monthly or annual terms", here for that in overall arrangements,
it results what the entire system more than less runs in ways then to either
run out its limits or make itself a sponsored effort, about more-or-less a simple
and responsible and accountable set of operations what effect the business
(here that in terms of service there is basically the realm of agreement)
that basically this sort of business-in-a-box model, is then besides itself of
accounts, toward the notion as pay-as-you-go and "usual credits and their limits".
Then for a news://usenet.science, or for example sci.math.usenet.science,
is the idea that the entity is "some assemblage what is so that in DNS, and,
in the accounts payable and receivable, and, in the material matters of
arrangement and authority for administration, of DNS and resources and
accounts what result durably persisting the business, is basically for a service
then of what these are usual enough tasks, as that are interactive workflows
and for mechanical workflows.
I.e. the point is for having the service than an on/off button and more or less
what is for a given instance of the operation, what results from some protocol
that provides a "durable store" of a sort of the business, that at any time basically
some re-routine or "eventually consistent" continuance of the operation of the
business, results basically a continuity in its operations, what is entirely granular,
that here for example the point is to "pick a DNS name, attach an account service,
go" it so results that in the terms, basically there are the placeholders of the
interactive workflows in that, and as what in terms are often for example simply
card and phone number terms, account terms.
I.e. a service to replenish accounts as kitties for making accounts only and
exactly limited to the one service, its transfers, basically results that there
is the notion of an email address, a phone number, a credit card's information,
here a fixed limit debit account that works as of a kitty, there is a regular workflow
service that will read out the durable stores and according to the timeliness of
their events, affect the configuration and reconciliation of payments for accounts
(closed loop scheduling/receiving).
https://datatracker.ietf.org/doc/draft-flanagan-regext-datadictionary/
https://www.rfc-editor.org/rfc/rfc9022.txt
Basically for dailies, monthlies, and annuals, what make weeklies,
is this idea of Internet-from-a- account, what is services.