Github user marcusgrando commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54241232
About the X- headers, maybe you guys can agree about one debug header like
X-Debug or another one and it can be used on the xdebug plugin too. Maybe a new
API
Github user zwoop commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54227923
Oh, and almost certainly, don't use std:string in the HttpSM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user zwoop commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54227662
Also, I'm not keen on naming headers like x-ats-uuid (we should not
introduce more X- headers into the wild).
---
If your project is set up for it, you can reply t
Github user zwoop commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54225453
But, if we exposed the http sm_id as both a log tag and plugin API, you
could do whatever you want? You could generate your own "UUID" based on the
sm_id? I'm assumi
Github user acaciocenteno commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54223450
The problem with HttpSM::sm_id is that it's just a counter, and as so it's
almost impossible to grep for it... the UUID, though, is guaranteed to be
unique.
Github user acaciocenteno commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/106#discussion_r17018609
--- Diff: proxy/http/HttpSM.cc ---
@@ -371,6 +392,107 @@ HttpSM::destroy()
httpSMAllocator.free(this);
}
+#ifdef TS_HAS_UUID
Github user SolidWallOfCode commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54215944
`HttpSM::sm_id` does not appear to be exposed to the plugin API, and I see
no reason that would be a problem. The example use cases are all from a single
r
Github user zwoop commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54215437
Yeah, I was just about to comment the same. the sm_id is a sequence number
though, and is not guaranteed unique across ATS instances.
---
If your project is set up
Github user SolidWallOfCode commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54215168
How is this different than `HttpSM::sm_id`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Hi all,
We’re looking at holding our next Summit in California, Bay Area (Sunnyvale /
Mountain View area). Assuming there is enough interest, the Summit will be a
2-day event. One of the takeaways from our last Summit was to break this up
into two types of sessions:
Day 1: Presentation
Github user bgaff commented on the pull request:
https://github.com/apache/trafficserver/pull/106#issuecomment-54208758
It appears there is no code in here to detect a previously set UUID, which
means that each tier will generate its own UUID, it would be nice if the
downstream could
Github user bgaff commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/106#discussion_r17011490
--- Diff: proxy/http/HttpSM.cc ---
@@ -371,6 +392,107 @@ HttpSM::destroy()
httpSMAllocator.free(this);
}
+#ifdef TS_HAS_UUID
+vo
Github user bgaff commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/106#discussion_r17011520
--- Diff: proxy/http/HttpSM.cc ---
@@ -371,6 +392,107 @@ HttpSM::destroy()
httpSMAllocator.free(this);
}
+#ifdef TS_HAS_UUID
+vo
Github user bgaff commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/106#discussion_r17011136
--- Diff: proxy/http/HttpSM.cc ---
@@ -371,6 +392,107 @@ HttpSM::destroy()
httpSMAllocator.free(this);
}
+#ifdef TS_HAS_UUID
+vo
GitHub user acaciocenteno opened a pull request:
https://github.com/apache/trafficserver/pull/106
Added Unique Identifier to HttpSM, to aid on debugging
While debugging the plugins we've written, we sometimes had trouble
correlating the log messages to one specific request. That
Tuesday, September 2, 2014, 3:04:55 AM, you wrote:
> How does ATS manage the expired objecs? If an object has expired/removed , I
> assume allocated space for it can later be used by other objects.
ATS doesn't have allocated space in the cache. It's a circular buffer. All
objects, including exp
Hi Allan,
How does ATS manage the expired objecs? If an object has expired/removed , I
assume allocated space for it can later be used by other objects.
Total size is pre-allocated for ATS, but using the allocated space effectively
is still an optimization. So I assume removing the duplicated
Ok, what about using a second ATS (parent of the first one) with a small
storage as buffering system?
18 matches
Mail list logo
