Re: Issue#3 -- Patch ready for HTTPS support

[Sasha Ovsankin]

Watsh --

Sorry I just saw your issue in http://code.google.com/p/json-rpc-client/issues/detail?id=3
. Somehow Google Code doesn't send me notifications when issues are
created.

I think it would be good idea to incorporate the HTTPS option
(assuming there are not too many dependencies to add to the project).

I am currently in the middle of adapting the library to the jabsorb
project and will be happy to incorporate your changes right after
that, probably in a couple of days.

Thanks,
-- Sasha

>>>
Hello Sasha,

I have recently had a chance to work with your excellent library and i
made
some small modification to the HttpSession.java to create a "https"
scheme
in r5 release source. I also had it tested with a self-signed
certificate
JSON RPC service (written using JSON-RPC-Java from metaparadigm). I am
not
sure if you will want to use it. Let me know if you are interested
and i
can send you the patch files.

Thanks,
W.
<<<

[#Cyrille37#]

Sasha Ovsankin a écrit :

> I am currently in the middle of adapting the library to the jabsorb

> project...
>
Thanks Sasha, it's a nice news.

Are changes will make json-rpc-client more heavy ?
I did not yet change my applications for using the new jabsorb, but when
your adaptation will be done, I'll have a try.

Cheers,
Cyrille.

[Sasha Ovsankin]

Cyrille --

In doesn't look like any changes to the library interface, so I guess
your code changes will be minimal.

Thanks,
-- Sasha

[Sasha Ovsankin]

Well actually, I had to downgrade the library to 1.4 removing all the
generics. So the Client.openProxy now returns Object and needs to be
casted.