> > It seems to me that after reading through the neo white paper that > > ColdFusion itself will be a J2EE app deployed in any > > Complient J2EE app server, > > No, they're currently only talking about compatibility specifically with > IBM > WebSphere, BEA WebLogic, and Macromedia JRun.
Those are the biggest and the best in the biz and the only ones really worth mentioning, whereby BEA is as far as I know is the best of them all and has by far more customers then say iPlanet. Sure JBoss would be nice, but that's open source, why bother. > > > and underneath is Java, and therefore this problem will be gone. > > I'm sorry, I still don't see how this follows. Java does have a lot more possibilities then CF. I know of several J2EE Servers that store either the whole or part of Application files directly in the DB. So, if these Servers (BEA being one of them) can already do this, why shouldn't I be able to do it with ColdFusion running on such a Server? Also, you will be able to mix CF with JSP tags, so you could probably write your own JSP customTag which uses Standard Java API's to do just that what this thread is all about. > > pre-compile ability and deployment is quite exciting though, am I right in > thinking that this'll remove the need to encrypt cfml files as they'll be > java bytecode? or is this just as vulnerable? I take it you will have Java Bytecode and therefore no need to encrypt your cfml files, but of course there are decomilers, but it is a little more difficult then decrypting CF Files (if that is even possible...:) > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: 14 November 2001 17:08 > > To: CF-Talk > > Subject: RE: binary stream (image) output to the browser > > > > > > It seems to me that after reading through the neo white paper that > > ColdFusion itself will be a J2EE app deployed in any > > Complient J2EE app server, > > therefore all your coldFusion code will be parsed by this > > J2EE app called > > ColdFusion, and underneath is Java, and therefore this > > problem will be gone. As well > > as a few other problems hopefully, like LOCKING!!!! > > hehe...not to mention the > > preformance boost.... > > > > > > All these problems will go away with neo... Because java does > > > > not share cf's > > > > weaknesses. > > > > > > Hmmm, neo will *still* be cfml, even if it is java based. > > Therefore it > > > doesn't necessarily follow that binary output problems will > > disappear in > > > the > > > next release. > > > > > > > -----Original Message----- > > > > From: Sicular, Alexander [mailto:[EMAIL PROTECTED]] > > > > Sent: 14 November 2001 16:43 > > > > To: CF-Talk > > > > Subject: RE: binary stream (image) output to the browser > > > > > > > > > > > > All these problems will go away with neo... Because java does > > > > not share cf's > > > > weaknesses. Needless to say java's support of binary objects > > > > is far greater > > > > then cf's. Btw, my cf and php applications work quite nicely > > > > together. > > > > > > > > Alexander Sicular > > > > Chief Technology Architect > > > > Neurological Institute of New York > > > > Columbia University > > > > as867 [at] columbia {dot} edu > > > > > > > > > > > > |-----Original Message----- > > > > |From: Franke, Ir. G.J. [mailto:[EMAIL PROTECTED]] > > > > |Sent: Wednesday, November 14, 2001 11:09 AM > > > > |To: CF-Talk > > > > |Subject: RE: binary stream (image) output to the browser > > > > | > > > > | > > > > |Thanx! perhaps an new feature for CF 6 or Neo? > > > > |cheers, Jappe > > > > | > > > > |> -----Original Message----- > > > > |> From: Sicular, Alexander [mailto:[EMAIL PROTECTED]] > > > > |> Sent: Wednesday, November 14, 2001 17:02 > > > > |> To: CF-Talk > > > > |> Subject: RE: binary stream (image) output to the browser > > > > |> > > > > |> > > > > |> not possible. i had many a long talk with many people at > > > > |> devcon about this > > > > |> very issue. unfortunately cf's binary handling is not the > > > > |> best. i use php > > > > |> on linux to do all my image/binary stuff. to use cf, you need > > > > |> to write to > > > > |> the hd. also uploading images to the db is done in base64, > > > > |> you need to write > > > > |> some sp's to convert from b64 to bin on the db. i don't > > > > |> recommend storing > > > > |> bin objects in the db as b64, less efficient (~30%). > > > > |> > > > > |> good luck, > > > > |> > > > > |> Alexander Sicular > > > > |> Chief Technology Architect > > > > |> Neurological Institute of New York > > > > |> Columbia University > > > > |> as867 {at} columbia [dot] edu > > > > |> > > > > |> -----Original Message----- > > > > |> From: Franke, Ir. G.J. [mailto:[EMAIL PROTECTED]] > > > > |> Sent: Wednesday, November 14, 2001 10:53 AM > > > > |> To: CF-Talk > > > > |> Subject: binary stream (image) output to the browser > > > > |> > > > > |> > > > > |> Hello there... does anyone know if it is possible to write an > > > > |> image stored > > > > |> in a variable, directly to the browser without writing it to > > > > |> the HDD first? > > > > |> > > > > |> <cfif server.os.name eq "Windows NT"> > > > > |> <cfobject type="COM" action="Create" > > class="top10.genmap" > > > > |> name="Bitmapper"> > > > > |> > > > > |> <cfset picture = Bitmapper(coords)> > > > > |> > > > > |> <cffile action="WRITE" > > > > |> file="C:\Inetpub\wwwroot\test\#coords#.jpg" > > > > |> output="#picture#" addnewline="No"> > > > > |> > > > > |> <cfoutput><img src="#coords#.jpg" > > border="0"></cfoutput> </cfif> > > > > |> > > > > |> this works... but how can i get it to work without the > > > > cffile action? > > > > |> > > > > |> > > > > |> > > > > | > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
