reply to:
Message: 5
Date: Tue, 30 May 2006 20:01:08 -0400
From: "Matthew Simpson" <[EMAIL PROTECTED]>
Subject: RE: [Flashcoders] self published.
To: "Flashcoders mailing list" <flashcoders@chattyfig.figleaf.com>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
I might stand alone on this but these questions popped into my mind
before I got to the second paragraph of your post: Why would I want
an open channel of communication between my applications (swf's) and
you? Why must your utility communicate with your servers? Why would
you not create your utility and make it available via the exchange as
a component instead?
------------------------------------------------------------------------
----------------------
- its a game or utility that allows real-time interaction with others.
- my server PUSHES data to your screen.
- its not designed for Flash developers to add into the site - its
designed for anyone with a moderate level of html skills to self
publish into a site.
- I may instead GIVE a URL link for them to embed or copy into their
site - but I want to know the benefits or cons for either method.
method a = embed a SWF in someones own domain and communicate with it
-- push data to it -- via XML socket?
method b = GIVE someone a referenced URL link that they embed into
their own site.
Does that make sense?
regards
Tj
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
