pplu / nrd Goto Github PK

The helo packet should transmit its contents in a data structure similar to the 
one used for results:

{ 'command' => 'helo', 'data' => { ... } }

That would simplify the serializers, possibly dropping the need to have the 
serializers tell the daemon that they "need a helo to work".

The helo packet should transmit its contents in a data structure similar to the 
one used for results:

{ 'command' => 'helo', 'data' => { ... } }

That would simplify the serializers, possibly dropping the need to have the 
serializers tell the daemon that they "need a helo to work".

The "none" serializer doesn't have an adequate name: it gives the impression 
that it doesn't serialize (which it does). This can be confusing.

A more adequate name would be "plain".

What steps will reproduce the problem?
1. Go to http://search.cpan.org/~jlmartin/NRD-Daemon-0.04/

What is the expected output? What do you see instead?
Expected license: GPL_3. Seen: GPL_1

Will have to separate the client and server so that passive results can be sent 
from a client without having to install the server dependencies

JSON will load JSON::XS if it's available, or a Pure Perl implementation if not.

Serializers and Writers have to be able to communicate what parameters they 
want passed to them, so that they can be communicated to Net::Server. 

Actually parameters have to be hard-coded into NRD::Daemon

Each IO operation on the server should be protected with an independent 
timeout, instead of one global timeout for the entire conversation between 
client and server.

Tests which have > in the results are replaced by "gt", what creates this 
behavior ? how can i keep the original output of a test when sent to the nrd 
server ?