Re: [PHP] Is php even right for this design?
William wrote: 1) Payroll apps require large tax libraries (federal, every state and locality). Split them into more files (diffrent states etc.) and include_once them when they are needed, and perhaps mysql can take part of the job. 4)Loosely Typed Variables. I fear it might be to simple in PHP to have a dollar amount converted to a string and become rounded or truncated, because php's loose type. This might be a smaller issue than I think? Is there a way to strictly enforce types/conversions so my numerics stay numerics? The issue is with floating point numbers, I encourage you to do the calculations in cents and round up when needed. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Is php even right for this design?
The admin users will need to run long processes that take about 5-15 minutes each. They cannot timeout and they must be done throughout the day while general users are working in the application as well. Is there a big problem with this? What steps should I take to ensure these long processes complete and do not timeout. What about turning these long processes into perl scripts or C programs that can be exec()ed? They'll probably run faster, and they won't time out. I've never done this myself. It's just a suggestion -- does it make sense to do it this way? Beau -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Is php even right for this design?
Beau Hartshorne wrote: The admin users will need to run long processes that take about 5-15 minutes each. They cannot timeout and they must be done throughout the day while general users are working in the application as well. Is there a big problem with this? What steps should I take to ensure these long processes complete and do not timeout. What about turning these long processes into perl scripts or C programs that can be exec()ed? They'll probably run faster, and they won't time out. I've never done this myself. It's just a suggestion -- does it make sense to do it this way? Best would be a PHP extension since it wouldn't need to be constantly reloaded :) Cheers, Rob. -- .-. | Robert Cummings | :-`. | Webdeployer - Chief PHP and Java Programmer | :--: | Mail : mailto:[EMAIL PROTECTED] | | Phone : (613) 731-4046 x.109 | :--: | Website : http://www.webmotion.com | | Fax : (613) 260-9545 | `--' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Is php even right for this design?
I don't know if this is possible, but in VB (I'd like to find something similar in php) I would open a record set, and then filter / unfilter it for similar issues (in a loop). I'm assuming you could use a similar approach somehow in php. Robert Cummings [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Beau Hartshorne wrote: The admin users will need to run long processes that take about 5-15 minutes each. They cannot timeout and they must be done throughout the day while general users are working in the application as well. Is there a big problem with this? What steps should I take to ensure these long processes complete and do not timeout. What about turning these long processes into perl scripts or C programs that can be exec()ed? They'll probably run faster, and they won't time out. I've never done this myself. It's just a suggestion -- does it make sense to do it this way? Best would be a PHP extension since it wouldn't need to be constantly reloaded :) Cheers, Rob. -- .-. | Robert Cummings | :-`. | Webdeployer - Chief PHP and Java Programmer | :--: | Mail : mailto:[EMAIL PROTECTED] | | Phone : (613) 731-4046 x.109 | :--: | Website : http://www.webmotion.com | | Fax : (613) 260-9545 | `--' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Is php even right for this design?
Jeff Bluemel wrote: I don't know if this is possible, but in VB (I'd like to find something similar in php) I would open a record set, and then filter / unfilter it for similar issues (in a loop). I'm assuming you could use a similar approach somehow in php. Sounds like a DB issue. Select your entries from your DB then loop through the result set with the same filtering mechanism. HTH, Rob. -- .-. | Robert Cummings | :-`. | Webdeployer - Chief PHP and Java Programmer | :--: | Mail : mailto:[EMAIL PROTECTED] | | Phone : (613) 731-4046 x.109 | :--: | Website : http://www.webmotion.com | | Fax : (613) 260-9545 | `--' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Is php even right for this design?
I don't know if this is possible, but in VB (I'd like to find something similar in php) I would open a record set, and then filter / unfilter it for similar issues (in a loop). I'm assuming you could use a similar approach somehow in php. Seems like a waste of resources. Why not do the filtering with the SQL query? Why are you selecting out more than you need? ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Is php even right for this design?
I am interested in writing a large scale, cross platform payroll/hr/gl appl entirely in php + mysql Innodb (for transaction support). I have 2 php programmers 1 asp/foxpro/access programmer to help me. I see 4 big hurdles to overcome in my php design: Large Libraries, Long Processes, Reporting, Loosely Typed Variables 1) Payroll apps require large tax libraries (federal, every state and locality). Now If I were interested in using ASP (which I'm not) I would probably compile these libraries into a .dll that would be loaded in-process with scripts that require it. Since I'm using Php I would most likely create a few really huge include files fedtax.inc.php,statetax.inc.php,localtax.inc.php that had all of my income tax calculations. I'm guessing these three libraries will be about 200Kb combined and need to be loaded often. Is it feasible to create such large includes for an app that will likely have 1000+users. Is there a better way to keep these functions available to my scripts without using these large includes? 2)Long Processes. There are 2 types of users...general and admin. There will be only about 5 administrators. The admin users will need to run long processes that take about 5-15 minutes each. They cannot timeout and they must be done throughout the day while general users are working in the application as well. Is there a big problem with this? What steps should I take to ensure these long processes complete and do not timeout. 3)Reporting. I think I can get by with HTML reports for the most part. however checks and tax forms require precisely positioned reporting abilities. I think that I will be better off using an external reporting application (crystal,access,FoxPro etc) to generate these reports. But if I do that then I'm sure I'll have to duplicate some of my coding efforts, since there is no way to achieve interop between these languages. Is there anyway to minimize the need to duplicate code? 4)Loosely Typed Variables. I fear it might be to simple in PHP to have a dollar amount converted to a string and become rounded or truncated, because php's loose type. This might be a smaller issue than I think? Is there a way to strictly enforce types/conversions so my numerics stay numerics? [Big application...Why would I want ot use PHP?] 1)The system can be developed on a laptop running xitami+win98 and then deployed on a high perfomance unix+apache machine without any adjustments :) 2)I won't be locked into vendor specific solutions (Sun EJB server/M$ .Net server) 3)I can teach the basics to new guys in about 1 week. 4)I just really like php, I've used it for 3 1/2 years and it's never failed me. But If there's a better framework for developing such an app, please let me know. Thanks a lot, Will -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Is php even right for this design?
1. Never had any problems with big includes before. 2. Maybe add a console based prog which sits in the background and process's jobs if you don't want to leave the web page open while it works, etc. 3. Make them PDF's (pdflib), we use it, and once you get programming in it, it's fairly easy. 4. I've never seen PHP round a number because it thought it was a string. =) Actually, if it's a string, it's more likely to interepret it as a don't touch me variable. (That makes sense to me anyway). Adam Voigt [EMAIL PROTECTED] On Thu, 2002-09-19 at 14:19, William wrote: I am interested in writing a large scale, cross platform payroll/hr/gl appl entirely in php + mysql Innodb (for transaction support). I have 2 php programmers 1 asp/foxpro/access programmer to help me. I see 4 big hurdles to overcome in my php design: Large Libraries, Long Processes, Reporting, Loosely Typed Variables 1) Payroll apps require large tax libraries (federal, every state and locality). Now If I were interested in using ASP (which I'm not) I would probably compile these libraries into a .dll that would be loaded in-process with scripts that require it. Since I'm using Php I would most likely create a few really huge include files fedtax.inc.php,statetax.inc.php,localtax.inc.php that had all of my income tax calculations. I'm guessing these three libraries will be about 200Kb combined and need to be loaded often. Is it feasible to create such large includes for an app that will likely have 1000+users. Is there a better way to keep these functions available to my scripts without using these large includes? 2)Long Processes. There are 2 types of users...general and admin. There will be only about 5 administrators. The admin users will need to run long processes that take about 5-15 minutes each. They cannot timeout and they must be done throughout the day while general users are working in the application as well. Is there a big problem with this? What steps should I take to ensure these long processes complete and do not timeout. 3)Reporting. I think I can get by with HTML reports for the most part. however checks and tax forms require precisely positioned reporting abilities. I think that I will be better off using an external reporting application (crystal,access,FoxPro etc) to generate these reports. But if I do that then I'm sure I'll have to duplicate some of my coding efforts, since there is no way to achieve interop between these languages. Is there anyway to minimize the need to duplicate code? 4)Loosely Typed Variables. I fear it might be to simple in PHP to have a dollar amount converted to a string and become rounded or truncated, because php's loose type. This might be a smaller issue than I think? Is there a way to strictly enforce types/conversions so my numerics stay numerics? [Big application...Why would I want ot use PHP?] 1)The system can be developed on a laptop running xitami+win98 and then deployed on a high perfomance unix+apache machine without any adjustments :) 2)I won't be locked into vendor specific solutions (Sun EJB server/M$ .Net server) 3)I can teach the basics to new guys in about 1 week. 4)I just really like php, I've used it for 3 1/2 years and it's never failed me. But If there's a better framework for developing such an app, please let me know. Thanks a lot, Will -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Is php even right for this design?
3)Reporting. I think I can get by with HTML reports for the most part. however checks and tax forms require precisely positioned reporting abilities. I think that I will be better off using an external reporting application (crystal,access,FoxPro etc) to generate these reports. But if I do that then I'm sure I'll have to duplicate some of my coding efforts, since there is no way to achieve interop between these languages. Is there anyway to minimize the need to duplicate code? Perhaps expose your report data as xml or even an xml service then your report writer can parse it or just use an xslt stylesheet to present the xml data. Just an idea -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Is php even right for this design?
1) Large Includes 200K of includes? Piece of cake! Remember, it is the server that is doing all of the work, not your clients. The issue is how many requests can your server simultaneously process and is there enough overhead to do it. With respect to speed, your server will cache the files after their first and repeated use, so you won't have to pull them from disk every single time. 2)Long Processes. 3)Reporting. Neither one of these things is a problem with PHP. The pdf library suggestion is a great one for reports. However, if it were me I would write a secondary app in my language of choice, like VB, foxpro, java, (but not access) which would still give me direct access to my data but would allow for some of the advanced admin/reporting tasks that PHP just didn't do well. Now, if everything must be web based, than you are limited to java or php or vbscript or other web langauges. 4)Loosely Typed Variables. mysql CAN BE very specific in it's typing requirements. PHP is a bit loose, but frankly html is looser. As the developer you have control to be as stricht as possible and validate/format all data any way you want. PHP has the tools to do this. me. 5.) But If there's a better framework for developing such an app, please let me know. Maybe there is, maybe there isn't. PHP will certainly drop the development time significantly. Give your requirements, I see no reason why you shouldn't move forward.
