what I do is setup a default project, no FDS and then when its time modify the .flexProperties file manually to turn on the server mode. Dimitrios Gianninas RIA Developer Optimal Payments Inc.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Merritt Sent: Wednesday, January 03, 2007 9:27 PM To: [email protected] Subject: Re: [flexcoders] Re: project set up: FDS ?? AMFPHP ?? WebOrb ?? Mark, thanks for the input. You confirmed what I was thinking, which was that i should set up the project using FDS, even if I do not plan to implement it right away. Keeping that in mind, I have a specific question as to how best to create the new project: Here is what I am doing... File - New Project [x] Flex Data Services [x] Compile Application Locally (can this be changed later?) Here is where I get stuck? If I was using FDS I would choose - [x] Use default local Flex Data Services Location For WebOrb they say to change the defaults to: Root Folder: "path to the /Weborb" I assume this is the local file path... Root URL: "http://localhost/Weborb <http://localhost/Weborb> " How about with AMFPHP. From my experience you don't need to set up a project as FDS when using AMFPHP, but since I am looking to the future I want to have the option later to change this. Should I just "Use default local Flex Data Services Location" or are there other settings that I should use? Can I use AMFPHP, WebOrb & FDS in the same app? I am sure this is confusing because I don't completely understand the files structure/content of how all these projects are set up.... Thanks for the help. - Kevin On Jan 3, 2007, at 12:31 PM, Mark Piller wrote: Hi Kevin, When choosing the type of a Flex Builder project you need to create, you need to decide how your Flex client will be communicating with the server. If you plan to use remoting, data management or messaging, then the project needs to be created using Flex Data Services, and here's why: Both FDS and WebORB support and expose the concept of destination which encapsulates the server-side logic your client can invoke or connect to. There are three types of destinations: remoting, data management and messaging. Each type is configured in remoting-config.xml, data-management-config.xml or messaging-config.xml, respectively. When your Flex Builder project is created to use Flex Data Services, it will contain special configuration/compilation parameters instructing Flex Builder to load these configuration files from the server. As a result, your Flex application is aware of the destinations registered on the server. To answer your question, I think it is a better practice to start a project with the type of client/server communication it will eventually use. Although it is possible to migrate from HttpService or WebService to RemoteObject in the middle of a project (and thus change the project type), I personally think it is an architectural type of decision and must be addressed before you even start coding. Hope this helps. Cheers, Mark --- In [EMAIL PROTECTED] <mailto:flexcoders%40yahoogroups.com> ups.com, Kevin Merritt <[EMAIL PROTECTED]> wrote: > > It's nice to have options, however, I am still continually confused > by which direction to go in terms of Data Services when designing my > applications. I have been an AMFPHP user for the past couple years > and have found it very useful and effective for what I need (the > newest beta looks great!). HOWEVER, the data sync & messaging > possibilities with FDS are something that I could really use in some > of my current project so I am very tempted to move in that > direction...once I have gotten a better hold on Flex & have the time > to learn Java. WebOrb PHP looks promising as well since it > ultimately plans to offer FDS type features. Keeping that in mind, > here are my questions: > > 1) Regardless of which technology I am going to use, should I always > set up my projects using Flex Data Services so that I have the option > to build that into the application down the road? If so, how to I > configure the Data Service Location wizard? (I notice that the > WebOrb set up has you start every new project using Flex Data > Service, but I don't think that is necessary with AMFPHP.) > > 2) How hard is it to add Flex Data Service to a project down the > road? I am developing my app using cairngorm so I am hoping this > will allow me to make these type of changes easier, however, I really > have no clue. > > My plan is too stick with AMFPHP for the time being, however, I just > want to make sure I am not headed down a path that will be hard to > change in the future should I want to integrate FDS. > > Thanks for the advice. Once I get this figured out I will happily > blog my progress to help answer these question for others. > > Thoroughly confused... > > - Kevin > -- WARNING ------- This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender. AVIS IMPORTANT -------------- Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur.
