PSFT - Fiscal 1998 - Discussion for the next year Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : PSFT - Fiscal 1998 - Discussion for the next year

PSFT 0.0001000

0.0%

Oct 29 5:00 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Lizzie Tudor who wrote (2004)	8/31/1998 2:10:00 PM
From: treetopflier	Read Replies (1) of 4509

Michelle, Your question goes to the heart of the matter. Who should own this code? If you want a router, that is ALREADY impossible for Cisco specialists to maintain (my brother is one of these), go ahead and start putting application specific code in it. Now who owns it? Who fixes it? Who coordinates releases as the app changes, or the router software needs to change? Who gets priority, PSFT this week, ORCL next? This is like fighting for home page space of portal vendors. This is a DUMB idea! As a former telecom manager the last thing I want is ANY application specific code in my network routing software. The Cisco environment is already WAY TOO COMPLEX to manage and maintain without having router code looking inside packets to see if they are Peoplesoft traffic. If Peoplesoft needs more performance, lighten up the client. Work on the Tuxedo integration. Tune the queries. But DON'T SCREW AROUND WITH THE NETWORK software in the routers and switches! ttf

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next