Github user cakofony commented on a diff in the pull request:

    https://github.com/apache/logging-log4j2/pull/206#discussion_r210290527
  
    --- Diff: 
log4j-redis/src/main/java/org/apache/logging/log4j/redis/appender/LoggingJedisPoolConfiguration.java
 ---
    @@ -0,0 +1,148 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements. See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache license, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License. You may obtain a copy of the License at
    + *
    + *      http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the license for the specific language governing permissions and
    + * limitations under the license.
    + */
    +
    +package org.apache.logging.log4j.redis.appender;
    +
    +import org.apache.logging.log4j.core.Core;
    +import org.apache.logging.log4j.core.config.plugins.Plugin;
    +import org.apache.logging.log4j.core.config.plugins.PluginAttribute;
    +import org.apache.logging.log4j.core.config.plugins.PluginBuilderFactory;
    +import redis.clients.jedis.JedisPoolConfig;
    +
    +/**
    + * Plugin configuration for {@link redis.clients.jedis.JedisPool} objects, 
allowing end users to set pool configuration
    + * if desired. If not set, will default to JedisPool defaults.
    + */
    +@Plugin(name = "PoolConfiguration", category = Core.CATEGORY_NAME, 
printObject = true)
    --- End diff --
    
    `PoolConfiguration` is fairly generic, thoughts on something along the 
lines of `RedisConnectionPool`?
    
    It may be worthwhile to name our classes in a way that references Redis 
rather than the Jedis library, that way we can change the implementation in the 
future without breaking library consumers.


---

Reply via email to