Tahoe-LAFS uses Foolscap extensively for logging but Tahoe-LAFS intends to drop its Foolscap dependency #3791

Open
opened 2021-09-08 10:57:52 +00:00 by exarkun · 0 comments
exarkun commented 2021-09-08 10:57:52 +00:00
Owner

A move completely away from Foolscap will be somewhat hampered by use of Foolscap's logging library. It is possible to use Foolscap's logging without using the network parts of Foolscap but it's not clear there is much reason to do so. There are some good reasons not to - such as avoiding the unnecessary complexity of using three different logging libraries.

Much of Foolscap logging's functionality overlaps with that of either Twisted or Eliot but there are some distinctive features - such as "incidents" - which will probably need a bit more careful thought to transition well.

A move completely away from Foolscap will be somewhat hampered by use of Foolscap's logging library. It *is* possible to use Foolscap's logging without using the network parts of Foolscap but it's not clear there is much reason to do so. There are some good reasons not to - such as avoiding the unnecessary complexity of using *three* different logging libraries. Much of Foolscap logging's functionality overlaps with that of either Twisted or Eliot but there are some distinctive features - such as "incidents" - which will probably need a bit more careful thought to transition well.
tahoe-lafs added the
unknown
normal
enhancement
n/a
labels 2021-09-08 10:57:52 +00:00
tahoe-lafs added this to the Non-Foolscap communications milestone 2021-09-08 10:57:52 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#3791
No description provided.