D3 socket calls and licensing

#11

Tony,

You need to read the later versions of the EULA. RD states that socket
connection must be persistant connection. Meaning that one socket server
one person, much like a serial port connection, or so I think.

Regards,

Dale

"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote

Quote:

If a PIB license is consumed by a phantom running a socket, that's not
too bad, considering the socket can be used to serve the needs of many
users, one at a time, but in quick succession. This is consistent
with FlashCONNECT which does consume D3 licenses even though it's run
on phantoms, and this usage does not violate the RD EULA. So running
nothing but socket clients you can get n-to-1 users per PIB license

What gets me about this, and again I haven't done any tests yet, is if
a phantom consumes a PIB license then you lose both the PIB and the
phantom. I wouldn't mind at all if they consumed a PIB license without
consuming the phantom license too. So a 20 user system could
conceivably run 15 phantom/sockets and 5 telnet PIBS, but still have
20 phantoms available for normal phantom use. Does anyone think this
is unreasonable? I think this model it's quite equitable.

Has anyone actually checked the behavior in a recent 7.4 release?

All that said, considering the hassles associated with sockets in
general I don't recommend anyone use them unless you really know how
to handle them (geeky pun sort of intended).

T

m buller <mabull_er_ (AT) jonaco (DOT) com> wrote:
Tony Gravagno wrote:
I haven't checked recently but I don't think socket
usage will cost an extra license on top of the one it's already
consuming. If I get some time I'll look at this but someone else's
confirmation would help.

A phantom using sockets will consume a user license and phantom license.

#12

Dale Benedict wrote:

Quote:

Tony,

You need to read the later versions of the EULA. RD states that
socket connection must be persistant connection. Meaning that one
socket server one person, much like a serial port connection, or so I
think.

It seems odd that RD is worried about enforcing one-to-one
relationships between users and connections to the database when they
sell a product such as the "D3 MQ Series Server Interface".

http://www.rainingdata.com/products/...mqi/index.html

Using message oriented middleware (MOM) such as IBM's MQ Series, which
is actually now called WebSphere MQ, one could easily service many
users via a single connection to D3.

http://www-306.ibm.com/software/integration/wmq/

--
Kevin Powick

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

D3 socket calls and licensing

comp.databases.pick comp.databases.pick

Re: D3 socket calls and licensing - 06-15-2005 , 10:51 AM

Re: D3 socket calls and licensing - 06-15-2005 , 01:04 PM