[Bug 61801] New: New function : Allow easy HEX and Base64 encode / Decode

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61801

            Bug ID: 61801
           Summary: New function : Allow easy HEX and Base64 encode /
                    Decode
           Product: JMeter
           Version: 3.3
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: p.mouawad@ubik-ingenierie.com
  Target Milestone: ---

_encodeDecode(string, mode,output variable) where mode is:
BASE64_ENCODE
BASE64_DECODE
HEX_ENCODE
HEX_DECODE

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61801] New function : Allow easy HEX and Base64 encode / Decode

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61801

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
Implementation provided with https://github.com/apache/jmeter/pull/530

I wonder, whether one function to encode and decode with a switch is a good
design. This is probably driven by the notion that too many functions are
already available.

This might be a good starting point to discuss how we can organize functions,
that there are not too many functions visible at the same time (in the docs, in
the code, in ...).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61801] New function : Allow easy HEX and Base64 encode / Decode

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61801

--- Comment #4 from Vladimir Sitnikov <si...@gmail.com> ---
I guess it is perfectly fine to have a bug id (so we can discuss it).

However, I don't feel the feature is ready for implementation yet.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61801] New function : Allow easy HEX and Base64 encode / Decode

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61801

--- Comment #2 from Vladimir Sitnikov <si...@gmail.com> ---
I agree with Felix, we should not combine unrelated functions under a single
name.

How base64 is related to hex?
What if the user wants upper case or lower case hex?

If the listed base64/hex encode/decode are required in core (?), they should be
4 distinct functions rather than a single one.

On top of that, it is not clear why input of encodeDecode is String.
Typically base64 is used to encode byte[] rather than a sting.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61801] New function : Allow easy HEX and Base64 encode / Decode

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61801

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hello,
I created this bugzilla a bit rapidly, when I further thought about it to
implement it , it looked less useful particularly when decoding to binary.

So I close it as is.
Let's discuss this before

Regards

-- 
You are receiving this mail because:
You are the assignee for the bug.