![]() | |
#11
| |||
| |||
|
|
I have to say I agree totally with Henry here. People seem to forget native Pick was WAY more than a database.It seems that while everyone was busy arguing that Pick was at least as good an Operating System as Unix, relational databases snuck up on the inside and stole the database crown. Pick ended up as an also ran in both the operating system and database fields. It could have been so different. And don't forget Microsoft were talking to Dick Pick before he died and they went the Access route. Still, Pick quietly supports plenty of businesses who really care about efficiency and value for money. The big problem is once those businesses grow past a certain size, get floated, start having turnover of line of management staff, and get invaded by graduates, Pick rapidly becomes a "Legacy" - a term synonymous with "Liability" to those aforementioned grads. If only ... csigline (AT) hotmail (DOT) com wrote: Joe wrote: I don't know if I'd go so far as to say that Pick can "run everything IT in a company." Pick is great for what it is, but IMO the key is knowing what solutions are best suited for the problems at hand. As for one-stop solutions, Microsoft probably has a better handle on that than Pick. ![]() Regards, Joe Joe: Obviously you also see value in the one-stop solution. That Pick can also be such a one-stop solution, "run everything IT in a company", is very simple to understand. I will limit myself to explaining this from the standpoint of using PowerPC because that's where my focus is http://www.ncolug.org/ppc.htm Ultimately, whatever the application is, it runs on the instruction set of the processor. So any application that runs on machines that are PowerPC based like the Apple G5 or the IBM pSeries, iSeries or zSeries can be made to not just run on Pick but those applications can also be made to run faster than they typically do now on some kind of OS because the overhead is so much less. Obviously running Pick natively on PowerPC requires some real programming with C and/or C++ and will require additions and/or modifications to those compilers. Doing so will also require additions and/or modifications to the DataBasic compiler but as a whole, those solutions are simpler and more cost effective than the Rube Goldberg solutions that have evolved to achieve the same objective. I am 100% convinced that, had there been Open Source solutions like drivers in the 1986 realm when OA was ported to AIX on the RT, Dick Pick would have been able to stick with the "everything on Pick" concept that had made Pick so extremely competitive as a business tool. It is a real shame that this genius did not live at least another ten years to take another shot at the IT crown. Henry Keultjes Microdyne Company Mansfield Ohio USA |
#12
| |||
| |||
|
#13
| |||
| |||
|
|
Joe: It's only a matter of time untill we see Microsoft expand their use of PowerPC (limited to the XBox right now) to the desktop and perhaps even the server. Henry Keultjes Microdyne Company Mansfield Ohio USA |
#14
| |||
| |||
|
|
I know this type of question has been asked numerous times but... What are the best, most cost effective ways to interface to D3 Windows and Linux from a web server (Apache)? We want to host a web service for our D3 systems to provide pricing, availability or whatever data is needed from D3 to an outside web site. The outside web site will be doing the presentation and shopping cart stuff. So, we are only interested in serving data at this time. I will be running Apache locally (Windows or Linux) to accept incoming requests, then I need to create a connection to D3 to run some programs to process the request and return some data. We are successfully doing this type of thing using JD3 (Apache/Tomcat/Java/JD3/D3) for one small project and it works fine, but I believe there are scalability issues and it seems like overkill. So, I know and accept that D3 user licences will be consumed but it has to be minimized or else it becomes too expensive, and licensing connectivity software (like Flashconnect) is not going to happen either. Thanks to all in advance, Steve check out http://www.sierra-bravo.com |
#15
| |||
| |||
|
#16
| |||
| |||
|
#17
| |||
| |||
|
#18
| |||
| |||
|
|
JD3 works using a port manager. A port manager listens on a main port and redirects requests from there to a worker port. Each worker port is a phantom process that sits and waits on a specific port for connections. I have not played with JD3 in years. I know that it fairly solid for an open source solution with a small developer base. JD3 is not a "web server interface" per se. It is a Java based OO interface for D3. You can use it for stand alone Java applications, as well as Java web applets. If you are keen on Java and you don't want to spend cash on R&D with non-free Java tools, then feel free to get your feet wet with it. I don't know that I'd want to sell commercial products with it, though. Just like MVWWW, it's really an open source design and development framework. It is functional, but it may not have the Q/C and testing that it should have to be released as a commercial tool. Besides, if I remember correctly it's GPL'd - so you can't bundle it with closed-source commercial products anyway. Glen |
#19
| |||
| |||
|
|
We use JD3 and python to read an e-mailed kanban pull (shipping request) with the data in an xml attachment. We use a python module to parse the xml data, then pass the data up to D3 and execute a program to process the pull. I have also played with python and wxwindows to demo a web like user interface between D3 and a pc client, it was nothing more then a proof of concept. Mark Buller Jonaco Machine |
#20
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |