varnish 4.0 support?

[xcir]

varnish 4.0 support?

[zstyblik]

As a matter of fact, most likely only (library) API has changed and the way how to attach to shared memory. May be some attributes(keys) has changed as well. Therefore, once API is brought up to date, once vsltrans is attached to shared memory again, I believe it will work. My colleague has confused me a bit with ``everything has changed''.

Anyway, we've ended up with parsing varnishlog's output for now. No manpower to pursue changes in API and how to attach it. It remains to be seen how it's going to cope with traffic.

[xcir]

vsltrans(support v4) is currently in development.(60%)
But, My regular work is busy now...
Please wait for 2 or 3 week.

[zstyblik]

@xcir, please, I was just correcting myself. vsltrans is FOSS, it comes free of charge and you have no obligation to anyone(in my opinion, my $0.02). Therefore, no apologies required on your side.

I've decided to use varnishlog instead, because:

• not enough experience to bring up VarnishAPI myself(=> a lot of time required to do so)
• my employer didn't give me more time
• number of lines is 50% of modified version of vsltrans(~ 300 V. 600)

It's probably suboptimal to parse varnishlog output from performance perspective. But it works and solution was required ASAP from management. I(we) will re-evaluate vsltrans once varnish 4.0 support is available :)

Thank you for all the work so far.

[xcir]

d11908e

support varnish4.0.x