|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
Complex Event Processing RSS News
StreamBase and the Progress Apama Trademark
Post 302158638 by Linux Bot on Wednesday 16th of January 2008 02:20:04 AM
01-16-2008
StreamBase and the Progress Apama Trademark
Tim Bass
Wed, 16 Jan 2008 07:02:37 +0000
Today I logged into to the blog-o-sphere to read this polite, but shocking, post by Chris Martins, Progress Apama,* The Power of the Apama Name.***
The post is shocking to me because it appears that StreamBase was blatantly abusing and violating the Apama trademark in a Google Adsense marketing campaign.
I find this hard to believe, and wonder if someone else, not StreamBase, was actually running this Adsense campaign.** I cannot imagine StreamBase doing something so ethically and legally wrong.*** I hope that*what we are seeing is an attack on StreamBase’s integrity and not an actual Adsense campaign by StreamBase.
From a legal perspective, StreamBase is liable for any loss of business or damages to Progress by wilfully violating the Apama trademark.
Frankly speaking, if StreamBase was responsible for this Adsense campaign memorialized in Chris’ post, then StreamBase owes Apama at a minimum, a*public apology.*
Source...
Wed, 16 Jan 2008 07:02:37 +0000
Today I logged into to the blog-o-sphere to read this polite, but shocking, post by Chris Martins, Progress Apama,* The Power of the Apama Name.***
The post is shocking to me because it appears that StreamBase was blatantly abusing and violating the Apama trademark in a Google Adsense marketing campaign.
I find this hard to believe, and wonder if someone else, not StreamBase, was actually running this Adsense campaign.** I cannot imagine StreamBase doing something so ethically and legally wrong.*** I hope that*what we are seeing is an attack on StreamBase’s integrity and not an actual Adsense campaign by StreamBase.
From a legal perspective, StreamBase is liable for any loss of business or damages to Progress by wilfully violating the Apama trademark.
Frankly speaking, if StreamBase was responsible for this Adsense campaign memorialized in Chris’ post, then StreamBase owes Apama at a minimum, a*public apology.*
Source...
|
|
We Also Found This Discussion For You
1. UNIX for Advanced & Expert Users
Hello All,
I am trying to extract a trademark character (™) from a varchar column in a DB2 Table. The result is to be placed in a sequential file in an AIX environment.
After the Extraction is complete when I view the extracted file I noticed that in place of the (™) Character another... (5 Replies)
Discussion started by: cosec
5 Replies
LEARN ABOUT DEBIAN
blaze-edit
BLAZE-EDIT(1) BlazeBlogger Documentation BLAZE-EDIT(1) NAME
blaze-edit - edits a blog post or a page in the BlazeBlogger repository SYNOPSIS
blaze-edit [-fpqCPV] [-b directory] [-E editor] id blaze-edit -h|-v DESCRIPTION
blaze-edit opens an existing blog post or a page with the specified id in an external text editor. Note that there are several special forms and placeholders that can be used in the text, and that will be replaced with a proper data when the blog is generated. Special Forms <!-- break --> A mark to delimit a blog post synopsis. Placeholders %root% A relative path to the root directory of the blog. %home% A relative path to the index page of the blog. %page[id]% A relative path to a page with the supplied id. %post[id]% A relative path to a blog post with the supplied id. %tag[name]% A relative path to a tag with the supplied name. OPTIONS
-b directory, --blogdir directory Allows you to specify a directory in which the BlazeBlogger repository is placed. The default option is a current working directory. -E editor, --editor editor Allows you to specify an external text editor. When supplied, this option overrides the relevant configuration option. -p, --page Tells blaze-edit to edit a page or pages. -P, --post Tells blaze-edit to edit a blog post or blog posts. This is the default option. -f, --force Tells blaze-edit to create an empty source file in case it does not already exist. If the core.processor option is enabled, this file is used as the input to be processed by the selected application. -C, --no-processor Disables processing a blog post or page with an external application. -q, --quiet Disables displaying of unnecessary messages. -V, --verbose Enables displaying of all messages. This is the default option. -h, --help Displays usage information and exits. -v, --version Displays version information and exits. ENVIRONMENT
EDITOR Unless the core.editor option is set, BlazeBlogger tries to use system-wide settings to decide which editor to use. EXAMPLE USAGE
Edit a blog post in an external text editor: ~]$ blaze-edit 10 Edit a page in an external text editor: ~]$ blaze-edit -p 4 Edit a page in nano: ~]$ blaze-edit -p 2 -E nano SEE ALSO
blaze-config(1), blaze-add(1), blaze-list(1) BUGS
To report a bug or to send a patch, please, add a new issue to the bug tracker at <http://code.google.com/p/blazeblogger/issues/>, or visit the discussion group at <http://groups.google.com/group/blazeblogger/>. COPYRIGHT
Copyright (C) 2008-2011 Jaromir Hradilek This program is free software; see the source for copying conditions. It is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Version 1.2.0 2012-03-05 BLAZE-EDIT(1)