Event Re-sender

New functionality: Event Re-sender
This new re-sender can open old data files and re-sends them back to the EUDAQ system. It registers itself as Producer. The name will be the name from the sub-event-type. 

This pull request includes the old pull request. 

ok resolved.
it's this one
https://github.com/eudaq/eudaq/pull/111/files#diff-15

On Wed, Dec 3, 2014 at 8:56 PM, Igor Rubinsky <igorrubinsky@googlemail.com>
wrote:

> yes, I am not :)
> ok, part of the push did not work.
> Simon I get this message. it's quite unusual to see this complaint:
>
> > git push rubinsky v1.4-dev-multiDC v1.4-dev-multiDC
> Username for 'https://github.com': rubinsky
> Password for 'https://rubinsky@github.com':
> error: dst ref refs/heads/v1.4-dev-multiDC receives from more than one src.
> error: failed to push some refs to 'https://github.com/rubinsky/eudaq.git'
>
> is there a common cure?
>
>
> On Wed, Dec 3, 2014 at 5:18 PM, simonspa <notifications@github.com> wrote:
>
>> In main/lib/src/TransportTCP.cc:
>>
>> > @@ -593,6 +628,7 @@ namespace eudaq {
>> >              EUDAQ_THROW_NOLOG(LastSockErrorString("SocketClient Error (" + to_string(LastSockError()) + ")"));
>> >            }
>> >            else if (result > 0){
>> > +			
>> >              m_buf.append(result, buffer);
>> >              while (m_buf.havepacket()) {
>> >                m_events.push(TransportEvent(TransportEvent::RECEIVE, m_buf, m_buf.getpacket()));
>>
>> Shouldn't you be on holidays? :)
>> And in PR111 I don't see the fix for that, just that you again set down
>> the msleep waiting times - which consistently crash on my system with
>> these settings...
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/eudaq/eudaq/pull/102/files#r21242285>.
>>
>
>