Good, thanks a lot for the feedback !
Sven
On 24 Oct 2013, at 12:05, Olivier Auverlot wrote:
> Hi Sven,
>
> Fantastic work ! I just tested the new version and it seem that all is ok.
>
> Olivier ;-)
>
>
Hi Sven,
Fantastic work ! I just tested the new version and it seem that all is ok.
Olivier ;-)
Hi Olivier,
Can you please test the latest Zn with your use case ?
You can load ConfigurationOfZincHTTPComponents from StHub and do
ConfigurationOfZincHTTPComponents project bleedingEdge load.
The are the relevant commits:
===
Name: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.22
Author:
Thanks for the improvement. Don't hesitate to contact me if I can help you
Olivier ;-)
Le 22 oct. 2013 à 18:49, Sven Van Caekenberghe a écrit :
>
> On 22 Oct 2013, at 18:27, "p...@highoctane.be" wrote:
>
>> Ok, point taken.
>>
>> Still, ZnClient is unusable for the intended purpose as is. No
On 22 Oct 2013, at 22:26, "p...@highoctane.be" wrote:
> BTW, I like the way you code clients and am learning a hefty bit from your
> damn great code :-)
>
> And I mean it.
Thanks!
BTW, I like the way you code clients and am learning a hefty bit from your
damn great code :-)
And I mean it.
On 22 Oct 2013, at 18:27, "p...@highoctane.be" wrote:
> Ok, point taken.
>
> Still, ZnClient is unusable for the intended purpose as is. No matter what
> encoding, % or not, Olivier cannot get the URL to work. Couldn't the ZnClient
> use something like the StampClient does: options? (where pr
Ok, point taken.
Still, ZnClient is unusable for the intended purpose as is. No matter what
encoding, % or not, Olivier cannot get the URL to work. Couldn't the
ZnClient use something like the StampClient does: options? (where
prefetch-count can be set for example - I also discovered the little in
On 22 Oct 2013, at 16:07, Sven Van Caekenberghe wrote:
> On 22 Oct 2013, at 15:49, "p...@highoctane.be" wrote:
>
>> I'd say you can encode @ with % in the URL (but it is not needed in any
>> case) indeed but in the rendered output? (Do you mean in hrefs="xxx" ?)
>>
>> Some things must be enc
On 22 Oct 2013, at 15:49, "p...@highoctane.be" wrote:
> I'd say you can encode @ with % in the URL (but it is not needed in any case)
> indeed but in the rendered output? (Do you mean in hrefs="xxx" ?)
>
> Some things must be encoded indeed:
>
> http://en.wikipedia.org/wiki/Character_entity
I'd say you can encode @ with % in the URL (but it is not needed in any
case) indeed but in the rendered output? (Do you mean in hrefs="xxx" ?)
Some things must be encoded indeed:
http://en.wikipedia.org/wiki/Character_entity_reference
http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_e
Hi Sven,
I'm totally agree with you. The Proxmox team had a bad idea to use @ but I must
find a solution to resolve the problem.
One solution could be to encode automaticaly the special characters in the url
but to let the possibility to desactivate the encoding with an option in
ZnClient. Th
Hi Olivier,
On 22 Oct 2013, at 09:57, Olivier Auverlot wrote:
> Hi,
>
> I work actually on a framework to manage a Proxmox server. The Proxmox
> solution is based on a strange REST API… :-(
>
> To get informations about an user, I must send a string with the login and
> the authentication do
Hi,
I work actually on a framework to manage a Proxmox server. The Proxmox solution
is based on a strange REST API… :-(
To get informations about an user, I must send a string with the login and the
authentication domain. The two values are separated by a character @.
For example: GET /api2/e
14 matches
Mail list logo
