[prev] [thread] [next] [lurker] [Date index for 2003/11/03]
This is a multi-part message in MIME format. ------=_NextPart_000_00FE_01C3A212.FE604960 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Often I see something in a piece of software that makes me think the = developers are a bunch of idiots. Something happened today that made me = think that they're just managed by people that don't understand how to = make software. We have some software that makes (mainly) static websites through = painful things like XML and XSLT (I have so much hate for these I don't = know where to begin). The net result is a bunch of HTML. We want to add = the ability to preview. Easy enough I chime in, just run a httpd on the = server and serve pages over the network.=20 That's too simple. The "solution" is to store the HTML compressed in a = database, write a client app to download it, uncompress it, fix the = absolute links, somehow get the images over the network and show = everything in an Internet Explorer control. The reasoning behind this = madness? If it's just on a network the user might give the ip address to = somebody and they'll browse it and be confused that the dynamic parts of = the website don't work. Worse is better. Gavin. ------=_NextPart_000_00FE_01C3A212.FE604960 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2>Often I see something in a piece of software that = makes me=20 think the developers are a bunch of idiots. Something happened today = that made=20 me think that they're just managed by people that don't understand how = to make=20 software.</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>We have some software that makes (mainly) static = websites=20 through painful things like XML and XSLT (I have so much hate for these = I don't=20 know where to begin). The net result is a bunch of HTML. We want to add = the=20 ability to preview. Easy enough I chime in, just run a httpd on the = server and=20 serve pages over the network. </FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>That's too simple. The "solution" is to store the = HTML=20 compressed in a database, write a client app to download it, uncompress = it, fix=20 the absolute links, somehow get the images over the network and show = everything=20 in an Internet Explorer control. The reasoning behind this madness? If = it's just=20 on a network the user might give the ip address to somebody and they'll = browse=20 it and be confused that the dynamic parts of the website don't=20 work.</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>Worse is better.</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>Gavin.</FONT></DIV></BODY></HTML> ------=_NextPart_000_00FE_01C3A212.FE604960--
Generated at 14:02 on 01 Jul 2004 by mariachi 0.52