Yep. Lots of people are using this. Lots. DataSnap is the new term for what Borland previously branded as their MIDAS technology, but due to trademark collisions, yada yada...
DataSnap is based around a couple of classes:
1. a TClientDataset class, which is responsible for representing an in-memory dataset which can be persisted as XML and has the capability to record offline dataset changes and post them back to the data persistence layer when necessary.
2. a TDatasetProvider, which links a TClientDataset to a persistence layer, such as a RBMS such as Oracle, MySQL, Interbase, DB2, or even (gasp) MSSQL. There is also an TXMLTransformProvider that can act as a 2 way mapping layer from a dataset to an XML document.
3. A TCustomRemoteServer descendant which supplies the remoting capability - placing the TClientDataSet and the TDataSetProvider on separate machines. These components can provide connections via HTTP, vanilla sockets, CORBA, etc.
There are also load balancing helpers to distribute the load.
And then there are the Web Services. Yep. That works too. It's SOAP, plain and simple.
We've got a DataSnap app deployed today, handling payroll data for ~1400 retail outlets. Heck, the TClientDataset class itself is worth the investment, even if you never build a n-tier system with it.
I think that I do have some measure of control over memory management in my machine, even though it doesn't crash when I tweak the registry. After all, most Windows 2000 power users are pretty tech-savvy.
This one is still seeing a chiropractor, and I haven't been on the road in 5 years. Try picking up a 600a 240/120v transformer for a couple of months. Not everybody limits their tours to the US.
The man said it: When they start handing out compulsory, national IDs, it's time to leave.
Re:Speed is very nice, but....
on
2.2 GHz Xeon
·
· Score: 1
Spending time coding a faster, more complex, less maintainable widget when you can buy a faster chip and use simpler, more maintainable code isn't always a very responsible decision to make. Commercial software, as a rule, should play to the lowest common denominator, but most programmers aren't writing shrink wrap. Balance the costs of writing AND maintaining the code with the cost of the hardware upgrade.
Don't buy till ya try. Really, the most important aspect of either one is how they make YOU feel. Not the price tag, not a big list of specs or features, NOTHING.
We started a new policy - every year, we purchase about 15 days worth of training vouchers from a good, local training firm for each person on the team. Every person on the team is guaranteed 15 days training per year, as long at it's somewhat, sorta relevant to what we do in general, not necessarily specific to a project. Oh, and we also get a $2000 tuition reimbursement, above and beyond the vouchers, for any class taken anywhere with a B or better grade.
Exagerating, to say the least. MS is neither the only game in town for Windows development, nor the best. 'Course, that said, I do have a MSDN Universal subscription, but it's pretty cheap for the stuff you get.
Disclaimer: I am an offensively rabid Delphi fan, and I think MS dev tools pretty much reek.
So, when technology advances to the point that any object - be it a blender, a Monet, or even a Pitz can be perfectly replicated ad infinitum, what happens? No more fine art, huh?
who needs speed with datasets that large? it's not like you're going to be doing anything more than playing large mpegs, right? i mean, why else would you need more memory?
Nice troll. I mean, I hope, anyway. You do know that, aside from the mundane DBMS application, there are all kinds of simulation software, rendering, etc that can use every GB of RAM you can throw at them.
too bad x86 will probably always be faster.
ROTFBMDOOMN
Yeah, right. We'll never need a different architecture. x86 will always be there.
I also know of a software shop, where the "other side" outnumbers a smaller, more productive group by five to one. But this time, the big group is AS/400 / AIX / DB2 / WebSphere / Java, and the smaller, more productive team uses Win2k / SQL Server / IIS / Delphi. What do either of these examples, by themselves, really prove? Probably the proficiency and adaptability of the team, and the fact that BOTH are using tools that really are up to the task.
perhaps what was being referred to was the incentive that quantum computers would bring to bear by making trad. crypto obsolete, thereby requiring more resources to be put into R&D for quantum crypto?
nahh. You'll actually see respect thrown out every once in a while for the seattle raised children of OS/2. The ones hated here are Win95/98/ME. At least, I hope so.
JP7. Its not flammable.
Pretty much. They use unsymmetrical Dimetheylhydrazine to light it off. The exotic motors are hybrid turbo/ramjets by GE.
Urban legend in the USAF has it that the SR-71 is Mach 4+
WHAAAT!! An informed SplashSlut reader? Someone who thinks that XP is more than pair programming?...then there's my favorite values: YAGNI and DTSTTCPW.
Polk or Klipsch speakers and Yamaha components, Adcom, Crest or Carver for amplifiers if you can afford it.
Also, try to go with a store that will let you try out a setup in your house - an acoustic environment probably completely unlike their store. Don't let anybody tell you what sound you like - it's YOUR ears!
Borland is working on Kylix and should be done soon (not like 2.4 soon, hopefully sooner!;)
It is a port of their (IMHO) superior Windows dev tools - Delphi and C++ Builder - to Linux.
Having had to hack SERIOUS projects in VB, I can comfortably say that, while it is a useful tool for simple projects, it quickly becomes unworkable. Pretend OO, crappy error handling model, and a slightly bittersweet candy shell.
Thank God for Delphi.
Slashdot Mirror
Yep. Lots of people are using this. Lots. DataSnap is the new term for what Borland previously branded as their MIDAS technology, but due to trademark collisions, yada yada...
DataSnap is based around a couple of classes:
1. a TClientDataset class, which is responsible for representing an in-memory dataset which can be persisted as XML and has the capability to record offline dataset changes and post them back to the data persistence layer when necessary.
2. a TDatasetProvider, which links a TClientDataset to a persistence layer, such as a RBMS such as Oracle, MySQL, Interbase, DB2, or even (gasp) MSSQL. There is also an TXMLTransformProvider that can act as a 2 way mapping layer from a dataset to an XML document.
3. A TCustomRemoteServer descendant which supplies the remoting capability - placing the TClientDataSet and the TDataSetProvider on separate machines. These components can provide connections via HTTP, vanilla sockets, CORBA, etc. There are also load balancing helpers to distribute the load.
And then there are the Web Services. Yep. That works too. It's SOAP, plain and simple.
We've got a DataSnap app deployed today, handling payroll data for ~1400 retail outlets. Heck, the TClientDataset class itself is worth the investment, even if you never build a n-tier system with it.
I think that I do have some measure of control over memory management in my machine, even though it doesn't crash when I tweak the registry. After all, most Windows 2000 power users are pretty tech-savvy.
Since when do roadies complain of back problems?
This one is still seeing a chiropractor, and I haven't been on the road in 5 years. Try picking up a 600a 240/120v transformer for a couple of months. Not everybody limits their tours to the US.
The man said it: When they start handing out compulsory, national IDs, it's time to leave.
Spending time coding a faster, more complex, less maintainable widget when you can buy a faster chip and use simpler, more maintainable code isn't always a very responsible decision to make. Commercial software, as a rule, should play to the lowest common denominator, but most programmers aren't writing shrink wrap. Balance the costs of writing AND maintaining the code with the cost of the hardware upgrade.
Don't buy till ya try. Really, the most important aspect of either one is how they make YOU feel. Not the price tag, not a big list of specs or features, NOTHING.
We started a new policy - every year, we purchase about 15 days worth of training vouchers from a good, local training firm for each person on the team. Every person on the team is guaranteed 15 days training per year, as long at it's somewhat, sorta relevant to what we do in general, not necessarily specific to a project. Oh, and we also get a $2000 tuition reimbursement, above and beyond the vouchers, for any class taken anywhere with a B or better grade.
Exagerating, to say the least. MS is neither the only game in town for Windows development, nor the best. 'Course, that said, I do have a MSDN Universal subscription, but it's pretty cheap for the stuff you get. Disclaimer: I am an offensively rabid Delphi fan, and I think MS dev tools pretty much reek.
I can.
And so this is where art notaries and curators and experts come in - to prove which is the original... and that is the one worth the most.
Really? What mad, supernatural art hacker skillz enable one to tell to perfectly identical objects apart?
So, when technology advances to the point that any object - be it a blender, a Monet, or even a Pitz can be perfectly replicated ad infinitum, what happens? No more fine art, huh?
Nice troll. I mean, I hope, anyway. You do know that, aside from the mundane DBMS application, there are all kinds of simulation software, rendering, etc that can use every GB of RAM you can throw at them.
too bad x86 will probably always be faster.
ROTFBMDOOMN
Yeah, right. We'll never need a different architecture. x86 will always be there.
I also know of a software shop, where the "other side" outnumbers a smaller, more productive group by five to one. But this time, the big group is AS/400 / AIX / DB2 / WebSphere / Java, and the smaller, more productive team uses Win2k / SQL Server / IIS / Delphi. What do either of these examples, by themselves, really prove? Probably the proficiency and adaptability of the team, and the fact that BOTH are using tools that really are up to the task.
perhaps what was being referred to was the incentive that quantum computers would bring to bear by making trad. crypto obsolete, thereby requiring more resources to be put into R&D for quantum crypto?
nahh. You'll actually see respect thrown out every once in a while for the seattle raised children of OS/2. The ones hated here are Win95/98/ME. At least, I hope so.
JP7. Its not flammable. Pretty much. They use unsymmetrical Dimetheylhydrazine to light it off. The exotic motors are hybrid turbo/ramjets by GE. Urban legend in the USAF has it that the SR-71 is Mach 4+
WHAAAT!! An informed SplashSlut reader? Someone who thinks that XP is more than pair programming? ...then there's my favorite values: YAGNI and DTSTTCPW.
Ohhh nooooo! More choices!!!!!!!!
the JCL has it's moments. I'd actually suggest the Delphi VCL first, but the source ain't free. Too bad - it's an excellent lesson in inheritance.
You know, the OS from the company y'all love to hate took some hints from VMS, and it also implements per-thread security.
Polk or Klipsch speakers and Yamaha components, Adcom, Crest or Carver for amplifiers if you can afford it. Also, try to go with a store that will let you try out a setup in your house - an acoustic environment probably completely unlike their store. Don't let anybody tell you what sound you like - it's YOUR ears!
Borland is working on Kylix and should be done soon (not like 2.4 soon, hopefully sooner! ;)
It is a port of their (IMHO) superior Windows dev tools - Delphi and C++ Builder - to Linux.
Having had to hack SERIOUS projects in VB, I can comfortably say that, while it is a useful tool for simple projects, it quickly becomes unworkable. Pretend OO, crappy error handling model, and a slightly bittersweet candy shell. Thank God for Delphi.
ya mean like profusion?