Gee, these are inciteful comments that dont really help the guy at all. (They incite me to be sarcastic)

Q1. How is the user who is already logged in authenticated? BlogCFC is using cfloginuser.




From: "Marcantonio" <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: <[email protected]>
Subject: RE: [CFCDev] Blog CFC mod help
Date: Sun, 11 Dec 2005 14:01:05 -0200

John,



I guess what you're proposing could be acquired with an adoption of the WSRP
standard (FAqs at:
http://www.oasis-open.org/committees/download.php/11774/wsrp-faq-draft-0.30.
html#portlet),

or maybe something similar to the JSR168 spec
(http://www.jcp.org/en/jsr/detail?id=168).

There is even an authentication standard XML schema,SAML (
http://www.oasis-open.org/committees/security/faq.php ).



Since CF is very very very straightforward, we don't usually adopt
standards. This really turns against us in the end.

Some time ago I had to develop a simple example on CF and Semantic web and
found out that there was no example on how to do it.

I found this article from some German researches where they say "We didn't
find toolkits for ActionScript and ColdFusion yet. Is there no Semantic Web
support for these languages?":

http://www.wiwiss.fu-berlin.de/suhl/bizer/toolkits/ , its sad to see that CF
simply gets out of the market because what we do can't be reused or applied
elsewhere.



Maybe is time for the CF community start defining our own standards, even
using the above standards fully or just as directions on how to start.

Defining our own standards would be simply and we could do it as anything in
CF: simple and direct.

Adopting an already existing standard would place our apps in a more broad
audience, using an WSRP standard, for a while,

would allow a CF app to be consumed by any web portal engine that supports
this standard, like IBM, Bea, Plumtree.

Anyway there are pros and cons in any way we decide.



Frameworks like Mach-ii,FB, MG or ColdSpring could have plugins that would
allow a developer to easily drop a blog inside his app, using common
authentication and rendering presentation methods.



Sure the more difficult would be to WRITE the standards in the first place,
then get the community to USE them, and I can see a number of different ways
on how to define common presentation layers,

maybe using a Flex-like XML language could do the work (again, Oasis has a
UIXML: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=uiml).



This would certainly get us, the CF community, stronger, getting the
"interoperability of CF apps" to work.





Regards,

Marcantonio Silva



  _____

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of John Farrar
Sent: domingo, 11 de dezembro de 2005 12:44
To: [email protected]
Subject: RE: [CFCDev] Blog CFC mod help



This is exactly why (different gains and losses to each approach) my desire
is to see a set of common API standards to allow applications to be built by multiple developers and integrated into a common system. There are two major
areas that are needed above the rest.



1.      Common authentication user management
2.      Common presentation layer (separating content from presentation)



I am not saying that only one system can do this, for certainly this could
be done in FB, Machii and others. Yet the lack of these standards existing
has prevented the code reuse on an application level. Currently the extent
of code reuse that is robustly integrated is on a CFC level, web services or
reusing single files within a site. There are some other examples of code
reuse. but for the most part you can't get a blog, calendar or other
application from an external source that integrates with your application
because there isn't a common standard to handle these issues with the more
popular methodologies. For all the benefits they bring to the table the lack
of application reuse or distribution is a tradeoff that small business in
particular cannot usually afford. The same would also be true for
departmental applications inside a corporation. The budget just isn't there
to write all the apps they need to have an effective site. and it isn't
going to happen until we catch on to this concept. (Note: These two items
are fundamental to building applications for any operating system; windows,
linux, etc. To continue to build applications without these standards is
like focusing our efforts on the DOS ages and forgetting how much window
based OS's with common system authentication have advanced computer usage.)



</rant>



John Farrar



  _____

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Billings, Brian J. (SMG)
Sent: Saturday, December 10, 2005 10:20 PM
To: [email protected]; [EMAIL PROTECTED]
Subject: [CFCDev] Blog CFC mod help



All,



I downloaded a copy of Blog CFC from Ray. What I want to do with it is put
it under my existing application name (nothing fancy) and allow any user
already logged in to act as an admin on the blog. I want to allow them to
post and comment showing their name on their posts.



I'm afraid to mess with some of the code I'm looking at. Has anyone that can
give me a few quick pointers done this already?






_________________________________________________________________
Over 100,000 new beginnings at Australia's #1 job site. http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2F&_t=752315885&_r=HM_EndText&_m=EXT



----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to