1

[system@pc]$ nc -v -l 10000  | gzip -d > output.file

Some details about the arguments and tools:

• nc: the BSD netcat tool implementation. There exists a GNU implementation often refered as gnu-netcat or netcat-traditional that can be launched either using the nc command or the netcat one.
• -l: listen to incoming TCP transmissions by default bounded to the default localhost hostname. A bounding hostname can be specified after the port number
• -v: verbose output through stderr output stream
• 10000: the listening port
• gzip -d: the gunzip compressor, the option -d sets it in decompressing mode. Since it has no more arguments, the compressed stream is extracted from the pipe and sink to the stdout stream.
• > output.file: redirects stdout stream to the file output.file in current working directory.

Then in the client side:

1

[system@pc]$ cat file.input | gzip | nc -v -w 30 myserver.domain.net 10000

About non previously commented arguments and commands:

• cat file.input |: display file.input content through the standard output stream and redirect it throug pipe.
• gzip |: without commands, compress data stream received from pipe and displays it through the standard output stream. It then redirects this output through pipe.
• | nc -v: transmits raw TCP packages generated from content received from pipe and display verbosed information.
• -w 30: timeout. If the pipe input stream is idle for more than 30 seconds or no connection can be established in that time the process is terminated. If no value is specified, there’s no timeout.
• myserver.domain.net 10000: the destination host name or IP address is myserver.domain.net and the listening port is 10000

The Carcaj Project Logo

Not, this is not yet a detailed explanation of what exactly is going to be the Carcaj Project (that will come in the follwing posts). I know that the project description is a bit confusing and not very specific, but we’re still at the preliminary stages of the project and in order to explain it properly I’d like to use very concrete examples that can be based on the first sketch of the system architecture. For now, please feel satisfied with the brief and original project description:

Carcaj will be an application-oriented ​NodeJS web framework focused in the development of application portals, i.e., web pages that contains very different utilities framed under the same user interface which share resources and code.

There is room for experimentation there, so the project will be guided by the objective of building a web portal with some very different small applications, with an special focus in testing different architectures and API designs.

On the other hand, this post is intended to summarize the main infrastructure and tools that will be used to track the Carcaj Project. I’ll try to briefly introduce all the resources and technologies that will be used as well as link it to theirs URLs. So, there we go:

• The Carcaj Project TRAC system - http://project.ajaest.net/carcaj/ - https://project.ajaest.net/carcaj/
  This will be the main project webpage, containing the documentation wiki, project organization documentation, ticketing system and and source code browse system. It’s based on the well known Trac system.
• The Carcaj Project GIT repository - http://git.rep.ajaest.net/carcaj - https://git.rep.ajaest.net/carcaj
  The source code control version system will be Git, almost all branches will be open since the begining for free cloning in a yet-to-deploy SSHed or HTTPSed system, what means that the links above are not up yet. The repo is already working but I have to configure a secure cloning edge point, so in the meanwhile you can browse or download the source code from the Trac portal’s “Browse Source” Tab.
• The Carcaj Project Blog and Feed - http://dottonetto.com/home/category/carcaj/
  In the blog I’ll mainly post large articles of heavy updates of the project, as well as specially relevant entries of the Trac’s portal Wiki. The URL above is really the “Carcaj” tag category reference of my personal blog Dottonetto in Spanish, but all Carcaj entries documentation and posts will be in English.
• The Carcaj Project Twitter account - https://twitter.com/CarcajProject
  In the twitter account I’ll publish any comment or deviation that crosses my mind related in even distant ways with the Carcaj Project, as well as references to the blog entries or updates related to the project or the technologies that it uses. It’s intended to become the most straightforward way to be up-to-date with the project status, and the main channel to get non-technical feedback about the project.

So, this it’s all. In following post I’ll try to explain more deeply about the objectives of the project, roadmapping and some preliminary technical information.See you!