I guess I need to ask the question, how much are these Eolas patent
changes going to affect email.


What is going to happen in IE is a pop-up box will prompt users as to
whether or not they want to see 'Active Content' in the browser, unless
you use scripting. I haven't seen anything about this affecting HTML
enabled email.


1) Is this really going to affect HTML email, or is this a browser
specific issue? As I understand it, this patent is specific to using Web
browsers to automatically load dynamic content through a plug-in, and
has nothing to do with HTML email. It it possible Outlook et al will not
be affected.


2) Is the pop-up box that intrusive? I realize it would be a pain to
have to hit a button each time one receives a Flash email, but I can
also imagine, and have seen, far worse.


Either way, I think this problem can be dealt with and you will not be
put out of business. Or you could possibly sue Eolas, I can't say why
but people have made cases against companies for far less and been
successful.


In the worst case, you can switch your business model to deploying
dynamic content using pure and pleasing ASCII art (which a large number
of people actually prefer). I am preparing to release a custom tag
expressly for the purpose of converting raster images into high-res
ASCII, if you want in on the beta please let me know.







-----Original Message-----
From: Jeff Beer [mailto:[EMAIL PROTECTED]
Sent: Friday, October 24, 2003 1:20 PM
To: CF-Talk
Subject: RE: Eolas patent suit


Dave is correct - scripting is out for e-mail messages - way too
many
variables to test for and manage, assuming you can even test.
We've
developed a way to allow the code to 'gracefully degrade' from
fully
scripted embedding of the OBJECT tag, to showing a standard jpg
image,
that works on almost all platforms.  But, if I can't get remote
data,
none of this matters any more.

Matt is also right - there's no way we can embed the flash
content in
the e-mail.  I can't send a 400k e-mail to 50k people.  The
users don't
mind some load time as there is a lot of static info that goes
with it.
However, people would (literally?) kill me if it took 30+
seconds to
download the message itself.

Even using base64 for the URI values, it's still external data,
and
won't load.  I don't currently see any way to do this, so I'm
hoping
that either MS gives in and buys a license, or, Eolas gets beat
down in
court, before the new browser versions come out.  Either way is
fine
with me :)





  _____  


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to