Open Bug 766166 Opened 7 years ago Updated 2 years ago
Have a service protocol to communicate with ssltunnel
This protocol should provide info and allow modifications of ssltunnel config at run-time like: - notification about ssltunnel server(s) is (are all) up and connections won't fail - support for startTLS, meaning after some exact byte start ssl nego - change certificates on server ports My suggestion is to have a js implemented server that runs in the host application. ssltunnel would be told to connect back to that server, the port would be given in the config file. This way it notifies us about being up and we can then use that socket to communicate.
Base for a service callback from ssltunnel. Currently implements only a timeout, startup and shutdown notification. At this moment ssltunnel doesn't read any commands from the client (controller) but it can be easily updated. This blocks an important patch for support of ssl in xpcshell tests. So I don't want to go with anything perfect and complicated right now. Try: https://tbpl.mozilla.org/?tree=Try&rev=7e49e50e189f
Assignee: nobody → honzab.moz
Status: NEW → ASSIGNED
Ted, I would like to ask for an advice here (instantiating a new component works locally, but not on try). I have introduced a new js implemented component ('@mozilla.org/ssltunnel-control;1') that is built along with ssltunnel program and copied to bin/components (.js + .manifest). This works for me locally, the component can be instantiated and works. But doesn't work (cannot be found in classes) on try server: https://tbpl.mozilla.org/?tree=Try&rev=aaa2f468c65d (then interesting changeset is https://hg.mozilla.org/try/rev/1b88d8b16feb) Changes to Makefile.in are taken from httpd.js Makefile.in. What am I doing wrong? Thanks.
Try: https://tbpl.mozilla.org/?tree=Try&rev=4f888e3be240 - very basic communication service protocol between ssltunnel and the host application (test-harness) - notifies about start of all configured servers and start up timeout - currently no way to configure ssltunnel remotely, but there is a good base to include such features easily (definitely for a followup) - ssltunnel-control.js is a test js module, no component
I got the necessary info.
Attachment #681466 - Flags: review?(ted) → review-
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #5) > Is there any reason to prefer writing this as a JS component instead of just > a JS module? The IDL doesn't add much value unless you plan on calling it > from C++. Ted, first, thanks for the review. According this question: My original intention was to have this as a component (hence the iface leftover too) and I put a lot of effort to achieve it, but it really was not that simple to do. There is also a discussion on dev-platform about this . I was trying hard, but that is really not that simple and people advised to rather have this as a module. If you can help (or even do) the actual work to turn this to a component, then I'll be very happy.  https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/o-p4kqie4oo
Assignee: honzab.moz → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.