![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
"Old" news now, but for those that aren't aware ... ftp://ftp.tigerlogic.com/pub/Windows...leaseNotes.pdf |
#3
| |||
| |||
|
|
It's interesting that TL named their .Net and Java communication protocol MVSP (multivalue server protocol). I wonder why a generic name instead of something "branded" like D3SP? Do you think they may wish other vendors to adopt MVSP as a standard? I don't see it mentioned anywhere that MVSP is an open protocol, so perhaps there's really no great meaning to the name at all. |
#4
| |||
| |||
|
|
As I understand it, the exact same MVSP product works exactly the same for both D3 and mvBase. |
|
MVSP is for MV people: - who don't understand why mv.NET is much better in the long term |
#5
| |||
| |||
|
|
From Newsgroup: comp.databases.pick - who don't understand why mv.NET is much better in the long term ....and don't mind that it's slower than even the VB5 version of the |
#6
| |||
| |||
|
|
It's interesting that TL named their .Net and Java communication protocol MVSP (multivalue server protocol). I wonder why a generic name instead of something "branded" like D3SP? Do you think they may wish other vendors to adopt MVSP as a standard? I don't see it mentioned anywhere that MVSP is an open protocol, so perhaps there's really no great meaning to the name at all. |
#7
| |||
| |||
|
|
On 2010-09-29 11:19:20 -0400, Tony Gravagno <nos... (AT) nospam (DOT) invalid> said: As I understand it, the exact same MVSP product works exactly the same for both D3 and mvBase. Right. Makes sense. MVSP is for MV people: - who don't understand why mv.NET is much better in the long term I know that mv.NET provides a much richer toolset and is more mature than MVSP, but to say that in the long run mv.NET would be better for *everyone* is certainly not true, nor can it be proven. For many, mv.NET *may* be the solution of choice. Btw, does mv.NET still rely on a relatively low throughput Telnet connection to D3 products? -- Kevin Powick |
#8
| |||
| |||
|
|
MVSP is for MV people: - who don't understand why mv.NET is much better in the long term I know that mv.NET provides a much richer toolset and is more mature than MVSP, but to say that in the long run mv.NET would be better for *everyone* is certainly not true, nor can it be proven. For many, mv.NET *may* be the solution of choice. |
|
Btw, does mv.NET still rely on a relatively low throughput Telnet connection to D3 products? |
![]() |
| Thread Tools | |
| Display Modes | |
| |