These are chat archives for ethersphere/orange-lounge
ethersphere orange lounge - swarm R & D - https://github.com/ethersphere/swarm/wiki/swarm - https://github.com/ethersphere/swarm/wiki/swarm-dev-progress -- subprojects working groups: https://github.com/ethersphere/swarm/wiki/Working-groups
@zelig I’ve been thinking about the discussion yesterday during the NetworkSim demo, about being able to track and visualise individual requests for GET/POST of content and chunks.
At the moment I find it hard to get the same behaviour from Swarm on my local node and when hitting swarm-gateways.net - it would be handy if there is a visual tool or at least a trace when you request a file.
If we have something like a
unique request id we could piggy-back it when retrieving a key/hash, and visualise the whole trace of a request within a cluster we control (just for test purposes). For example attaching the request id as part of log lines, together with atomic increment / step, so that we can review one request from one swarm node to another.
Is this something you might find useful, or have you discussed something similar?
generateId, however it is part of swarm/network, whereas if it is generated immediately upon receiving the origin HTTP request, tracing would be easier
another question i have - https://github.com/ethereum/go-ethereum/pull/15198/files - i see that you are moving away for using the
global logger and introducing one that belongs to the Node. what’s the rational behind this? to me it looks like the log structure is all the same, and we might as well be using the global log, provided it is initialised immediately when starting the node. every service that needs a log from then on, can just use it, rather than embed it everywhere.
i guess you had a reason to plug it in Node though
Making your calendar public will make all events visible to the world, including via Google search. Are you sure?
parameters that are sensitive:
retryInterval set in
keepAliveInterval set in
ìfchecks in the API handler