Bug #31897 | tunneling a mysql connection through http(s) | ||
---|---|---|---|
Submitted: | 27 Oct 2007 23:49 | Modified: | 5 Nov 2022 1:46 |
Reporter: | Don Cohen | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | Connector / J | Severity: | S4 (Feature request) |
Version: | OS: | Any | |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[27 Oct 2007 23:49]
Don Cohen
[8 Sep 2009 6:58]
Tonci Grgin
Hi Don and thanks for your report. Taking a quick glance over the latest code I do not find this implemented thus verified as described. Mark?
[8 Sep 2009 14:55]
Mark Matthews
I played around this a long time ago, and it's very, very slow, because of the nature of the mysql protocol (or any thing that isn't batch-y enough). It seems to make more sense to create a RESTful web service where the granularity as at the domain object level and push the persistence concerns to your server, and let the applet interact via HTTP with the domain object model, or to pull the granularity up higher and build actual services?
[8 Sep 2009 17:58]
Don Cohen
It's interesting to see a reply out of the blue after almost 2 years. I did end up using ids software and yes it was a major problem to convert. It's slower but not enormously so. I don't understand the second reply. What's a RESTful web service? What do you mean by granularity at domain object level? What's an actual service? How are these things supposed to help? Also, SQL seems pretty batch-y to me.
[5 Nov 2022 1:46]
Filipe Silva
Feature not in the Connector/J development plan.