Best Of
Ice and Unix Domain Sockets
Hi,
I saw in other posts that it is possible to implement Ice on a different lay of transport.
Unix domain sockets particularly interest me, because if I use Ice, I use it locally. And, as I have seen with omniORB or Thrift, unix sockets seem to be faster than TCP. So I would like to use unix sockets with Ice.
The problem is that I am a beginner, only a second year's student. I read that we can be helped by the source code which is already present, with TcpAcceptor, TcpConnector... etc. But could you give me a little bit more details about that ? The steps to follow ?
Thank you.
Clement
Re: Performance of asynch twoway vs oneway proxies
Hi Diego,
The performance for these two calls should be very similar, one thing to keep in mind oneway->call(); will throw an exception if there is an error sending, begin_call, waitForSent or waitForComplete will not.
If you want to handle exception after waitForSent you have to add an additional call to throwLocalException()
auto t = twoway->begin_call(); t->waitForSent(); t->throwLocalException();
Otherwise, if you want to handle exceptions after completion call the end method twoway->end_call(t) to wait for the completion and this will report any exceptions.
xdm
Re: IceSSL: Additional failure info accessible from the low level SSL engine?
Hey Jose,
I think this might be something on our end . We do open up two connections on start for different reasons which would explain those verifications. And something in our shutdown for our program might be errantly trying to re-establish the connection. I should have done a bit more debugging before reaching out. I got additional feedback from another developer right after I posted this to you.
thanks
Jeremy
Re: Is there a way to still have a property called "Value" on a class now that Value is a reserved word?
Hi Michael,
You can use \Value see https://doc.zeroc.com/ice/3.7/the-slice-language/lexical-rules#id-.LexicalRulesv3.7-EscapedIdentifiers
Cheers,
Jose
xdm
Re: IceSSL: Additional failure info accessible from the low level SSL engine?
Hi Jose,
Sorry to waste your time. Indeed I had a different version of our cert generator that was intentionally making them invalid installed. I didn't pay close enough attention to that before reaching out to you. I thought it had been working on Windows but I realized I was testing my CA signed cert path. All is good, thanks again!
Jeremy
Re: IceSSL: Additional failure info accessible from the low level SSL engine?
Jose,
The getHost() change works like a champ. Thanks again for the super-fast turnaround.
Jeremy
Re: IceGrid with Javascript/Typescript
Hi Sergio,
We don't have any JavaScript demos for this but it should work, the JavaScript generated code for IceGrid service is provided with our JavaScript distribution. You will have to configure IceGrid to listen on a WebSocket endpoint or set up a WebSocket proxy that forwards the connections to IceGrid.
Cheers,
Jose
xdm
Re: Centos 7: /usr/lib64/php/modules/ice.so: undefined symbol: zval_used_for_init
Thank you so much to give me a path forward !
Fenryll
Re: Slice2java - How to add command option (i.e. --underscore) to Ant Task Def
Thanks much xdm!!! In fact I was looking at the ant-ice code too, but could not figure it out. Your first option works (adding to the ice file). I will also try your second option for completeness. Again Thanks much!!!
Re: How to ensure that glacier can offer a similar experience to all connections going through it?
Hi Victor,
There's no built-in features in Glacier2 to provide this functionality and I'm afraid there's no trivial solutions to support this.
It could done at the firewall level if the firewall provides functionality to allow sharing the bandwidth between clients. This might be too coarse grained however if you want to limit the bandwidth based on application specific criteria (e.g. privileged vs non-privileged users). This also requires having administrative access to the firewall.
Another option is to implement your own router to suite your specific needs or implement a facade server for that clients would connect to and which would forward traffic to Glacier2. It would allow to perform bandwidth/latency limitations. We could provide some consulting to help you implementing this.
Yet another option is to improve Glacier2 to allow intercepting requests received from clients to perform bandwidth/latency limitations. Glacier2 could either provide a mechanism to allow applications to install an interceptor for this purpose or it could implement it internally and provide some configuration.
Cheers,
Benoit