You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@esme.apache.org by bu...@apache.org on 2011/06/27 15:55:31 UTC
svn commit: r791676 [3/8] - /websites/staging/esme/trunk/content/
Added: websites/staging/esme/trunk/content/collaboration-with-ubimic.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/collaboration-with-ubimic.cwiki (added)
+++ websites/staging/esme/trunk/content/collaboration-with-ubimic.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,61 @@
+{section:border=true}
+{column:width=70%}
+
+h4. Background
+
+[http://ubimic.org]. is a group of university researchers interested in microblogging from different points of view (computer science, information systems, organizational science). Together we think that microblogging has great potential when it comes to integrating normal users and things like sensors, machines and software. We are experimenting with different microblogging tools and scenarios.
+
+h3. SAP Bot
+{gliffy:name=ubimic - SAP Bot|space=ESME|page=Collaboration with ubimic|pageid=5964323|align=left|size=S}
+
+h4. General Use Case
+
+The idea is to show how microblogging can act as a integration platform for man-machine interaction.
+# The user creates mesages on Apache ESME with a certain tag and having a certain format
+# The Apache ESME bot listens to the Apache ESME message stream for messages with a certain tag.
+# After receiving messages from Apache ESME with the desired tag, the Apache ESME bot reformats the message and posts the message to an SAP back-end.
+# Based on the status of the back-end interaction, the Apache ESME bot posts an Apache ESME message with the status of the interaction.
+
+h4. Technical details
+
+* The Apache ESME Bot could be developed in any language but we have examples code for accessing the REST API for clients written in [Java|http://svn.apache.org/repos/asf/incubator/esme/trunk/esme-java-client/] and [ABAP|http://code.google.com/p/esmeproject/source/browse/#svn/trunk/esme-abap].
+* The access to the SAP system could be performed via various means (web-services, RFC call, etc.) depending on what sort of system (version, etc.) you guys have on the university.
+* There are two ways to get data from Apache ESME via a bot.
+** You can access the Apache ESME core directly via API - polling for messages
+** You can set an [action|http://cwiki.apache.org/confluence/display/ESME/Actions]that responds to certain tags and then calls your Apache ESME bot via an HTTP call. We've done something like this for forwarding messages to twitter.
+
+{column}
+{column:width=30%}
+
+h4. Use Cases
+
+h5. Use Messages for Back-end Requests
+
+* The idea here would be to use Apache ESME to ask the back-end for certain pieces of information.
+* Example: "@sapstockbot how many T60 laptops do we have in stock?". The answer could be "@boehr there are 3 items left where 2 are already booked. Till now, no orders for new items are in the system."
+* Example: "@sappurchaseorders I need 4 new T60 laptops for #projectx asap\!" and the bot creates the Purchase Order in the system on behalf of the project manager's user name (if he has the rights for this).
+* Business users may have difficulty in using such systems, so text analysis of the messages is very useful. Research work in this direction is promising (for example, "[TextAnalysis in Information Streams: Status Quo and Future Perspectives|http://www.tu-chemnitz.de/wirtschaft/wi2/wp/en/2009/08/10/text-analysis-in-information-streams-status-quo-and-future-perspectives/]"
+* One idea might be to use the code for the [SAP ES Google Wave Bot|http://wave-samples-gallery.appspot.com/about_app?app_id=31006]from [Daniel Graversen|http://wave-samples-gallery.appspot.com/profile?id=63059] that uses Enterprise Service (ES) data to post to a blip. The code is available. *{_}Note{_}{*}_: just looked at the code. It would very easy to re-use it have a ESME bot that queries an ES that returns a material_
+* [Details|ESME:Use Case - Posting from SAP back-end]
+
+h5. Microblogging SAP System
+
+* There is an Apache ESME pool that is restricted to certain individuals (for example, accounting staff, which reports about latest paid orders). Origin of this group should probably be container-based (for example, LDAP).
+* The SAP back-end is also a member of this group (for example, the user "sappaidorders") and posts messages to the group like "Order XYZ has been paid by customer KN30292938".
+* Let's say order XYZ is very valuable but there were problems with the customer. The accounting person would then say "RT @sappaidorders Order XYZ has been paid by customer KN30292938 // well, finally. Good work guys\!".
+* Based on ESME's pool concept, this message would only be visible to individuals in this pool.
+* The different permission schemes between the microblogging environment and the backend would also be a topic to be examined.
+* Example of research in this area: "[Microblogging and ERP systems: use cases and prototype|http://www.tu-chemnitz.de/wirtschaft/wi2/wp/en/2009/08/10/microblogging-and-erp-systems-use-cases-and-prototype/]"
+
+h5. Taskmanagement
+
+* See the suggestion for task-related mesages used by [Remember the Milk|http://www.rememberthemilk.com]for its [Twitter format|http://www.rememberthemilk.com/services/twitter/]
+* The SAP back-end system must be a xRPM
+
+h5. Device-related Use Case
+
+* RFID-enhanced devices send messages to microblogging system
+* Use case should also describe why inclusion of microblogging system brings advantages over direct data insertion into back-end system.
+
+{column}
+{section}
\ No newline at end of file
Added: websites/staging/esme/trunk/content/collaboration-with-ubimic.html
==============================================================================
--- websites/staging/esme/trunk/content/collaboration-with-ubimic.html (added)
+++ websites/staging/esme/trunk/content/collaboration-with-ubimic.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,177 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Collaboration with ubimic</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Collaboration with ubimic</h1>
+ <p>{section:border=true}
+{column:width=70%}</p>
+<p><a name="Collaborationwithubimic-Background"></a></p>
+<h4 id="background">Background</h4>
+<p><a href="http://ubimic.org">http://ubimic.org</a>
+. is a group of university researchers interested in microblogging from
+different points of view (computer science, information systems,
+organizational science). Together we think that microblogging has great
+potential when it comes to integrating normal users and things like
+sensors, machines and software. We are experimenting with different
+microblogging tools and scenarios.</p>
+<p><a name="Collaborationwithubimic-SAPBot"></a></p>
+<h3 id="sap_bot">SAP Bot</h3>
+<p>{gliffy:name=ubimic - SAP Bot|space=ESME|page=Collaboration with
+ubimic|pageid=5964323|align=left|size=S}</p>
+<p><a name="Collaborationwithubimic-GeneralUseCase"></a></p>
+<h4 id="general_use_case">General Use Case</h4>
+<p>The idea is to show how microblogging can act as a integration platform for
+man-machine interaction.
+1. The user creates mesages on Apache ESME with a certain tag and having a
+certain format
+1. The Apache ESME bot listens to the Apache ESME message stream for
+messages with a certain tag.
+1. After receiving messages from Apache ESME with the desired tag, the
+Apache ESME bot reformats the message and posts the message to an SAP
+back-end.
+1. Based on the status of the back-end interaction, the Apache ESME bot
+posts an Apache ESME message with the status of the interaction.</p>
+<p><a name="Collaborationwithubimic-Technicaldetails"></a></p>
+<h4 id="technical_details">Technical details</h4>
+<ul>
+<li>The Apache ESME Bot could be developed in any language but we have
+examples code for accessing the REST API for clients written in <a href="http://svn.apache.org/repos/asf/incubator/esme/trunk/esme-java-client/">Java</a>
+ and [ABAP|http://code.google.com/p/esmeproject/source/browse/#svn/trunk/esme-abap]
+.</li>
+<li>The access to the SAP system could be performed via various means
+(web-services, RFC call, etc.) depending on what sort of system (version,
+etc.) you guys have on the university.</li>
+<li>There are two ways to get data from Apache ESME via a bot.
+<strong> You can access the Apache ESME core directly via API - polling for
+messages
+</strong> You can set an <a href="http://cwiki.apache.org/confluence/display/ESME/Actions">action</a>
+that responds to certain tags and then calls your Apache ESME bot via an
+HTTP call. We've done something like this for forwarding messages to
+twitter.</li>
+</ul>
+<p>{column}
+{column:width=30%}</p>
+<p><a name="Collaborationwithubimic-UseCases"></a></p>
+<h4 id="use_cases">Use Cases</h4>
+<p><a name="Collaborationwithubimic-UseMessagesforBack-endRequests"></a></p>
+<h5 id="use_messages_for_back-end_requests">Use Messages for Back-end Requests</h5>
+<ul>
+<li>The idea here would be to use Apache ESME to ask the back-end for certain
+pieces of information.</li>
+<li>Example: "@sapstockbot how many T60 laptops do we have in stock?". The
+answer could be "@boehr there are 3 items left where 2 are already booked.
+Till now, no orders for new items are in the system."</li>
+<li>Example: "@sappurchaseorders I need 4 new T60 laptops for #projectx
+asap!" and the bot creates the Purchase Order in the system on behalf of
+the project manager's user name (if he has the rights for this).</li>
+<li>Business users may have difficulty in using such systems, so text analysis of the messages is very useful. Research work in this direction is promising (for example, "<a href="http://www.tu-chemnitz.de/wirtschaft/wi2/wp/en/2009/08/10/text-analysis-in-information-streams-status-quo-and-future-perspectives/">TextAnalysis in Information Streams: Status Quo and Future Perspectives</a>
+"</li>
+<li>One idea might be to use the code for the <a href="http://wave-samples-gallery.appspot.com/about_app?app_id=31006">SAP ES Google Wave Bot</a>
+from [Daniel Graversen|http://wave-samples-gallery.appspot.com/profile?id=63059]
+ that uses Enterprise Service (ES) data to post to a blip. The code is
+available. <em>{<em>}Note{</em>}{</em>}<em>: just looked at the code. It would very easy to
+re-use it have a ESME bot that queries an ES that returns a material</em></li>
+<li><a href="esme:use-case---posting-from-sap-back-end.html">Details</a></li>
+</ul>
+<p><a name="Collaborationwithubimic-MicrobloggingSAPSystem"></a></p>
+<h5 id="microblogging_sap_system">Microblogging SAP System</h5>
+<ul>
+<li>There is an Apache ESME pool that is restricted to certain individuals
+(for example, accounting staff, which reports about latest paid orders).
+Origin of this group should probably be container-based (for example,
+LDAP).</li>
+<li>The SAP back-end is also a member of this group (for example, the user
+"sappaidorders") and posts messages to the group like "Order XYZ has been
+paid by customer KN30292938".</li>
+<li>Let's say order XYZ is very valuable but there were problems with the
+customer. The accounting person would then say "RT @sappaidorders Order XYZ
+has been paid by customer KN30292938 // well, finally. Good work guys!".</li>
+<li>Based on ESME's pool concept, this message would only be visible to
+individuals in this pool.</li>
+<li>The different permission schemes between the microblogging environment
+and the backend would also be a topic to be examined.</li>
+<li>Example of research in this area: "<a href="http://www.tu-chemnitz.de/wirtschaft/wi2/wp/en/2009/08/10/microblogging-and-erp-systems-use-cases-and-prototype/">Microblogging and ERP systems: use cases and prototype</a>
+"</li>
+</ul>
+<p><a name="Collaborationwithubimic-Taskmanagement"></a></p>
+<h5 id="taskmanagement">Taskmanagement</h5>
+<ul>
+<li>See the suggestion for task-related mesages used by <a href="http://www.rememberthemilk.com">Remember the Milk</a>
+for its [Twitter format|http://www.rememberthemilk.com/services/twitter/]</li>
+<li>The SAP back-end system must be a xRPM</li>
+</ul>
+<p><a name="Collaborationwithubimic-Device-relatedUseCase"></a></p>
+<h5 id="device-related_use_case">Device-related Use Case</h5>
+<ul>
+<li>RFID-enhanced devices send messages to microblogging system</li>
+<li>Use case should also describe why inclusion of microblogging system
+brings advantages over direct data insertion into back-end system.</li>
+</ul>
+<p>{column}
+{section}</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/collaborations-with-other-organizations.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/collaborations-with-other-organizations.cwiki (added)
+++ websites/staging/esme/trunk/content/collaborations-with-other-organizations.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,9 @@
+Our intention is to collaborate with as many different organizations as possible in order to provide the best value for those using this technology.
+
+
+
+|| Organization || Description \\ || Status \\ ||
+| akibot | [Akibot|http://akibot.blogspot.com/] is the first semantic actionable micro-blogging platform for the enterprise. Akibot not only allows real-time group collaboration and awareness through short, instant messages (like a Twitter for the company), but it also understands those messages and, if applicable, takes action. | [Overview and detailed use case available|ESME:Collaboration with Akibot]\\ |
+| OFBiz \\ | [The Apache Open For Business Project|http://ofbiz.apache.org/] is an open source enterprise automation software project licensed under the Apache License Version 2.0. By open source enterprise automation we mean: Open Source ERP, Open Source CRM, Open Source E-Business / E-Commerce, Open Source SCM, Open Source MRP, Open Source CMMS/EAM, and so on. | [Initial brainstorming|http://cwiki.apache.org/confluence/display/ESME/Collaboration+with+OFbiz]\\ |
+| Thingamy | [http://thingamy.com/|http://thingamy.com/] Thingamy the Work processor adds a framework to the whole process of delivering a value, it be a service or a product. It starts out with a template closely suitable to your business workflow - project, legal advice, advertising, whatever - and lets you tweak the process. | [Overview and use cases|http://cwiki.apache.org/confluence/display/ESME/Collaboration+with+Thingamy]\\ |
+| \#ubimic | [http://ubimic.org|http://ubimic.org/]. is a group of university researchers interested in microblogging from different points of view (computer science, information systems, organizational science) | [Use case description currently in progress|ESME:Collaboration with ubimic]\\ |
Added: websites/staging/esme/trunk/content/collaborations-with-other-organizations.html
==============================================================================
--- websites/staging/esme/trunk/content/collaborations-with-other-organizations.html (added)
+++ websites/staging/esme/trunk/content/collaborations-with-other-organizations.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,74 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Collaborations with other Organizations</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Collaborations with other Organizations</h1>
+ <p>Our intention is to collaborate with as many different organizations as
+possible in order to provide the best value for those using this
+technology.</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/database-scheme.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/database-scheme.cwiki (added)
+++ websites/staging/esme/trunk/content/database-scheme.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,4 @@
+Below you can see the database scheme for the current Apache ESME server. This might be especially relevant for those developing administration applications.
+
+
+!1195121.jpg|border=1!
Added: websites/staging/esme/trunk/content/database-scheme.html
==============================================================================
--- websites/staging/esme/trunk/content/database-scheme.html (added)
+++ websites/staging/esme/trunk/content/database-scheme.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Database Scheme</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Database Scheme</h1>
+ <p>Below you can see the database scheme for the current Apache ESME server.
+This might be especially relevant for those developing administration
+applications.</p>
+<p>!1195121.jpg|border=1!</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.cwiki (added)
+++ websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,76 @@
+{section}
+{column:width=70%}
+
+h4. General Use case
+
+# A new user visits the ecommerce site
+# This new user enters a microblog message with a question to the administrator of the site.
+# One of the system administrators answers the microblog question as quick as possible
+# Further conversation follows.
+
+h4. Technical Prerequisites
+
+* You would need an Apache ESME instance (either on a separate server or in the same container).
+* You would need at least two users (administrator, newuser) "newuser" would *not be* associated with a particular user but would be more of an anonymous user. If you had multiple unauthenticated users using the same e-commerce site, then they would also see / join the same conversation. Depending on the question, they might be able to help the new user as well.
+
+
+h4. Technical Description
+
+The basic idea is that an OFBiz UI will be created to capsule the Apache ESME functionality
+
+
+
+h4. Apache ESME as separate component
+
+
+{gliffy:name=ESME - OFBiz collaboration - Separate|space=ESME|page=ESME as Chat+ in OfBiz|pageid=9373498|align=left|size=M}
+
+
+h4. Apache ESME as OFBiz component
+
+
+
+
+h5. Advantges
+
+
+* let it use the OFBiz authentication
+* allows Apache ESME to use essential system functions like system messages and ease of installation
+
+
+h2. Prototype
+
+# Deploy Apache ESME in your existing tomcat
+# Create two users in Apache ESME: newuser and administrator.
+# Create a very rough OfBiz UI component to read and post Apache ESME messages. This is the UI for new users. Use the token for the new users in this UI
+# The administrator could use the same OfBiz UI component but you have to set the token to the administrator user.
+# If you don't want to deploy Apache ESME locally, then you could use [our test server in the cloud|http://esmecloudserverapache.dickhirsch.staxapps.net/]
+
+
+h2. Thoughts on authentication
+
+Obviously, the goal would be to have some sort of a common authentication between Apache ESME and OFBiz. In the basic use case, all you really need are two users - anonymous and administrator. Anonymous would be for those users who are not administrators. Since I'm assuming that chat would be available for all users, this would mean that users would see the conversations between other users and the administrators. This would also mean that all users could participate in such conversations.
+
+
+In future iterations of the OfBiz / Apache ESME collaboration, other options would be available.
+
+Currently, Apache ESME has its own user administration and can't use the user administration from the container. We are looking at various means to overcome this gap but we haven't had time to implement them yet. This means that initially there would be a double administration of users. Adding, deleting users and changing user properties would have to occur twice - once in Apache ESME and once in OfBiz. One way to get around this would be to expand our API to deal with such administrative tasks.
+
+Since our APis are based on tokens, you would need to store a token in the user object in OFBiz that could later be used when making calls to Apache ESME.
+
+
+
+{column}
+{column:width=30%}
+*Contents*
+{toc}
+
+
+*Iterations*
+
+# Use Apache ESME as a separate component
+# Make Apache ESME an OFBiz component
+
+
+{column}
+{section}
\ No newline at end of file
Added: websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.html
==============================================================================
--- websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.html (added)
+++ websites/staging/esme/trunk/content/esme-as-chat-in-ofbiz.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,155 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - ESME as Chat in OfBiz</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">ESME as Chat in OfBiz</h1>
+ <p>{section}
+{column:width=70%}</p>
+<p><a name="ESMEasChatinOfBiz-GeneralUsecase"></a></p>
+<h4 id="general_use_case">General Use case</h4>
+<ol>
+<li> A new user visits the ecommerce site</li>
+<li>This new user enters a microblog message with a question to the
+administrator of the site.</li>
+<li>One of the system administrators answers the microblog question as quick
+as possible</li>
+<li>Further conversation follows.</li>
+</ol>
+<p><a name="ESMEasChatinOfBiz-TechnicalPrerequisites"></a></p>
+<h4 id="technical_prerequisites">Technical Prerequisites</h4>
+<ul>
+<li>You would need an Apache ESME instance (either on a separate server or in
+the same container). </li>
+<li>You would need at least two users (administrator, newuser) "newuser"
+would <em>not be</em> associated with a particular user but would be more of an
+anonymous user. If you had multiple unauthenticated users using the
+same e-commerce site, then they would also see / join the same
+conversation. Depending on the question, they might be able to help the new
+user as well.</li>
+</ul>
+<p><a name="ESMEasChatinOfBiz-TechnicalDescription"></a></p>
+<h4 id="technical_description">Technical Description</h4>
+<p>The basic idea is that an OFBiz UI will be created to capsule the Apache
+ESME functionality</p>
+<p><a name="ESMEasChatinOfBiz-ApacheESMEasseparatecomponent"></a></p>
+<h4 id="apache_esme_as_separate_component">Apache ESME as separate component</h4>
+<p>{gliffy:name=ESME - OFBiz collaboration - Separate|space=ESME|page=ESME as
+Chat+ in OfBiz|pageid=9373498|align=left|size=M}</p>
+<p><a name="ESMEasChatinOfBiz-ApacheESMEasOFBizcomponent"></a></p>
+<h4 id="apache_esme_as_ofbiz_component">Apache ESME as OFBiz component</h4>
+<p><a name="ESMEasChatinOfBiz-Advantges"></a></p>
+<h5 id="advantges">Advantges</h5>
+<ul>
+<li>let it use the OFBiz authentication</li>
+<li>allows Apache ESME to use essential system functions like system messages
+and ease of installation</li>
+</ul>
+<p><a name="ESMEasChatinOfBiz-Prototype"></a></p>
+<h2 id="prototype">Prototype</h2>
+<ol>
+<li>Deploy Apache ESME in your existing tomcat</li>
+<li>Create two users in Apache ESME: newuser and administrator. </li>
+<li>Create a very rough OfBiz UI component to read and post Apache ESME
+messages. This is the UI for new users. Use the token for the new users in
+this UI</li>
+<li>The administrator could use the same OfBiz UI component but you have to
+set the token to the administrator user. </li>
+<li>If you don't want to deploy Apache ESME locally, then you could use <a href="http://esmecloudserverapache.dickhirsch.staxapps.net/">our test server in the cloud</a></li>
+</ol>
+<p><a name="ESMEasChatinOfBiz-Thoughtsonauthentication"></a></p>
+<h2 id="thoughts_on_authentication">Thoughts on authentication</h2>
+<p>Obviously, the goal would be to have some sort of a common authentication
+between Apache ESME and OFBiz. In the basic use case, all you really need
+are two users - anonymous and administrator. Anonymous would be for those
+users who are not administrators. Since I'm assuming that chat would be
+available for all users, this would mean that users would see the
+conversations between other users and the administrators. This would also
+mean that all users could participate in such conversations.</p>
+<p>In future iterations of the OfBiz / Apache ESME collaboration, other
+options would be available. </p>
+<p>Currently, Apache ESME has its own user administration and can't use the
+user administration from the container. We are looking at various means to
+overcome this gap but we haven't had time to implement them yet. This means
+that initially there would be a double administration of users. Adding,
+deleting users and changing user properties would have to occur twice -
+once in Apache ESME and once in OfBiz. One way to get around this
+would be to expand our API to deal with such administrative tasks.</p>
+<p>Since our APis are based on tokens, you would need to store a token in the
+user object in OFBiz that could later be used when making calls to Apache
+ESME.</p>
+<p>{column}
+{column:width=30%}
+<em>Contents</em></p>
+<p><em>Iterations</em></p>
+<ol>
+<li>Use Apache ESME as a separate component</li>
+<li>Make Apache ESME an OFBiz component</li>
+</ol>
+<p>{column}
+{section}</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/esme-desktop-client-server-config.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/esme-desktop-client-server-config.cwiki (added)
+++ websites/staging/esme/trunk/content/esme-desktop-client-server-config.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,22 @@
+h1. How to configure the ESME server ESME Desktop connects to ..
+
+By default ESME Desktop connects to the ESME instance running at http://www.esme.us, but if you are running your own instance of the server, you will need to change the server that ESME Desktop connects to .. here's how ..
+
+This setting is stored in your application storage directory in a file called preferences.xml ... the application storage directory path varies based on your operating system and your username
+
+h1. MacOS:
+
+/Users/username/Library/Preferences/ESMEDesktop.05D8320A56ED876B4DC203B7387C89522DDC092F.1/Local Store/preferences.xml The GUID in the path may vary.
+
+h1. Windows:
+
+C:\Documents and Settings\username\Application Data\ESMEDesktop.05D8320A56ED876B4DC203B7387C89522DDC092F.1\Local Store\preferences.xml
+
+If the file does not exist create preferences.xml and drop in the following xml and save .. <preferences> <preference name="ESME_APISERVER" value="http://api.esme.us/esme/api/"/> <preference name="ESME_SERVER" value="http://www.esme.us/esme/"/> </preferences>
+If the file exists then edit the values to your server urls. The new setting will be picked up the next time you start ESME Desktop.
+
+An example preferences file. The value for _token_ is from the Manage Tokens link, after you log in via the web. <preferences>
+ <preference name="ESME_APISERVER" value="http://api.esme.us/esme/api/"/>
+ <preference name="ESME_SERVER" value="http://www.esme.us/esme/"/>
+ <preference name="token" value="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"/>
+</preferences>
\ No newline at end of file
Added: websites/staging/esme/trunk/content/esme-desktop-client-server-config.html
==============================================================================
--- websites/staging/esme/trunk/content/esme-desktop-client-server-config.html (added)
+++ websites/staging/esme/trunk/content/esme-desktop-client-server-config.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - ESME Desktop Client Server Config</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">ESME Desktop Client Server Config</h1>
+
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/esme-installation-guides.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/esme-installation-guides.cwiki (added)
+++ websites/staging/esme/trunk/content/esme-installation-guides.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,58 @@
+h4. Windows
+
+* [Windows Vista|http://cwiki.apache.org/confluence/display/ESME/Windows+Vista+Installation+Guide]\\
+
+* [Windows XP - Revision 885445|http://cwiki.apache.org/confluence/display/ESME/Windows+XP+Installation+Guide+%28revision+885445%29]
+
+h4.
+\\
+
+h4. Mac OS X
+
+* [10.6|http://cwiki.apache.org/confluence/display/ESME/Mac+OS+X+10.6+Installation+Guide]\\
+
+h4.
+\\
+
+h4. Linux
+
+
+* [Debian - Ubuntu|http://cwiki.apache.org/confluence/display/ESME/Linux+%28Debian+-+Ubuntu%29+Installation+Guide]
+
+h4.
+\\
+
+h4. Cloud
+
+* [Stax|ESME:Stax]
+
+h4.
+\\
+
+h4. SAP Netweaver Composition Environment (CE)
+
+
+* [7.1|ESME:CE Installation Guide] (_Note_: Still a work in progress)
+
+
+h4.
+\\
+
+h4. ESME Mailet Install Guide
+
+* [EMSE Mailet Install Guide|http://cwiki.apache.org/confluence/display/ESME/ESME+Mailet+Install+Guide]\\
+
+
+\\
+
+h4. Java Servlet Container Installation Guide
+
+* [Java Servlet Container Installation Guide]\\
+
+
+\\
+
+h4. Desktop Client Server Config
+
+* [ESME Desktop Client Server Config]\\
+\\
\ No newline at end of file
Added: websites/staging/esme/trunk/content/esme-installation-guides.html
==============================================================================
--- websites/staging/esme/trunk/content/esme-installation-guides.html (added)
+++ websites/staging/esme/trunk/content/esme-installation-guides.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,110 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - ESME Installation Guides</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">ESME Installation Guides</h1>
+ <p><a name="ESMEInstallationGuides-Windows"></a></p>
+<h4 id="windows">Windows</h4>
+<ul>
+<li><a href="http://cwiki.apache.org/confluence/display/ESME/Windows+XP+Installation+Guide+%28revision+885445%29">Windows XP - Revision 885445</a></li>
+</ul>
+<p><a name="ESMEInstallationGuides-"></a></p>
+<h4 id="" />
+<p><a name="ESMEInstallationGuides-MacOSX"></a></p>
+<h4 id="mac_os_x">Mac OS X</h4>
+<p><a name="ESMEInstallationGuides-"></a></p>
+<h4 id="_1" />
+<p><a name="ESMEInstallationGuides-Linux"></a></p>
+<h4 id="linux">Linux</h4>
+<ul>
+<li><a href="http://cwiki.apache.org/confluence/display/ESME/Linux+%28Debian+-+Ubuntu%29+Installation+Guide">Debian - Ubuntu</a></li>
+</ul>
+<p><a name="ESMEInstallationGuides-"></a></p>
+<h4 id="_2" />
+<p><a name="ESMEInstallationGuides-Cloud"></a></p>
+<h4 id="cloud">Cloud</h4>
+<ul>
+<li><a href="esme:stax.html">Stax</a></li>
+</ul>
+<p><a name="ESMEInstallationGuides-"></a></p>
+<h4 id="_3" />
+<p><a name="ESMEInstallationGuides-SAPNetweaverCompositionEnvironment(CE)"></a></p>
+<h4 id="sap_netweaver_composition_environment_ce">SAP Netweaver Composition Environment (CE)</h4>
+<ul>
+<li><a href="esme:ce-installation-guide.html">7.1</a>
+ (<em>Note</em>: Still a work in progress)</li>
+</ul>
+<p><a name="ESMEInstallationGuides-"></a></p>
+<h4 id="_4" />
+<p><a name="ESMEInstallationGuides-ESMEMailetInstallGuide"></a></p>
+<h4 id="esme_mailet_install_guide">ESME Mailet Install Guide</h4>
+<p><a name="ESMEInstallationGuides-JavaServletContainerInstallationGuide"></a></p>
+<h4 id="java_servlet_container_installation_guide">Java Servlet Container Installation Guide</h4>
+<p><a name="ESMEInstallationGuides-DesktopClientServerConfig"></a></p>
+<h4 id="desktop_client_server_config">Desktop Client Server Config</h4>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/esme-mailet-install-guide.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/esme-mailet-install-guide.cwiki (added)
+++ websites/staging/esme/trunk/content/esme-mailet-install-guide.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,3 @@
+The ESME Mailet is a plugin for theOpen source [Mail Server Apache James|http://james.apache.org/server/], which allows users of an ESME infrastructure (both humans and technical systems) to send email messages to an ESME instance using their own identity. Messages sent through the mailet show up as personal messages from these end users, so people following you get them in the respective blogging timeline.
+
+You will find the guide (PDF) and the ESMEMailet.jar file under Attatchments.
\ No newline at end of file
Added: websites/staging/esme/trunk/content/esme-mailet-install-guide.html
==============================================================================
--- websites/staging/esme/trunk/content/esme-mailet-install-guide.html (added)
+++ websites/staging/esme/trunk/content/esme-mailet-install-guide.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,79 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - ESME Mailet Install Guide</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">ESME Mailet Install Guide</h1>
+ <p>The ESME Mailet is a plugin for theOpen source <a href="http://james.apache.org/server/">Mail Server Apache James</a>
+, which allows users of an ESME infrastructure (both humans and technical
+systems) to send email messages to an ESME instance using their own
+identity. Messages sent through the mailet show up as personal messages
+from these end users, so people following you get them in the respective
+blogging timeline.</p>
+<p>You will find the guide (PDF) and the ESMEMailet.jar file under
+Attatchments. </p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/esme-privacy-policy.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/esme-privacy-policy.cwiki (added)
+++ websites/staging/esme/trunk/content/esme-privacy-policy.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,29 @@
+Last Updated: July 14, 2009
+
+Information about your use of this website is collected using a tracking cookie. The collected information consists of the following:
+
+The IP address from which you access the website;
+# The type of browser and operating system you use to access our site;
+# The date and time you access our site;
+# The pages you visit; and
+# The addresses of pages from where you followed a link to our site.
+
+Part of this information is gathered using a tracking cookie set by the [Google Analytics|http://www.google.com/analytics/] service and handled by Google as described in their [privacy policy|http://www.google.com/privacy.html]. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.
+
+We use the gathered information to help us make our site more useful to visitors and to better understand how and when our site is used. We do not track or collect personally identifiable information or associate gathered data with any personally identifying information from other sources.
+
+By using this website, you consent to the collection of this data in the manner and for the purpose described above.
+
+Occasionally, at our discretion, we may include links to other third party content or services on our website. These third party sites have separate and independent privacy policies and therefore we have no responsibility or liability for the content and activities of these linked sites.
+
+
+If we make changes to our privacy policy, we will send a notification to our mailing lists <us...@esme.apache.org> and <de...@esme.apache.org> along with updating the "Last Updated" date at the top of this page.
+
+If there are any questions regarding this privacy policy, you can contact us on the following mailing list <pr...@esme.apache.org>.
+
+\\
+
+Sincerely,
+The Apache ESME PMC
+
+\\
\ No newline at end of file
Added: websites/staging/esme/trunk/content/esme-privacy-policy.html
==============================================================================
--- websites/staging/esme/trunk/content/esme-privacy-policy.html (added)
+++ websites/staging/esme/trunk/content/esme-privacy-policy.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,100 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - ESME Privacy Policy</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">ESME Privacy Policy</h1>
+ <p>Last Updated: July 14, 2009</p>
+<p>Information about your use of this website is collected using a
+tracking cookie. The collected information consists of the following:</p>
+<p>The IP address from which you access the website;
+1. The type of browser and operating system you use to access our site;
+1. The date and time you access our site;
+1. The pages you visit; and
+1. The addresses of pages from where you followed a link to our site.</p>
+<p>Part of this information is gathered using a tracking cookie set by the <a href="http://www.google.com/analytics/">Google Analytics</a>
+ service and handled by Google as described in their [privacy policy|http://www.google.com/privacy.html]
+. See your browser documentation for instructions on how to disable the
+cookie if you prefer not to share this data with Google.</p>
+<p>We use the gathered information to help us make our site more useful to
+visitors and to better understand how and when our site is used. We do not
+track or collect personally identifiable information or associate gathered
+data with any personally identifying information from other sources.</p>
+<p>By using this website, you consent to the collection of this data in the
+manner and for the purpose described above.</p>
+<p>Occasionally, at our discretion, we may include links to other third party
+content or services on our website. These third party sites have separate
+and independent privacy policies and therefore we have no responsibility or
+liability for the content and activities of these linked sites.</p>
+<p>If we make changes to our privacy policy, we will send a notification to
+our mailing lists <a href="mailto:user@esme.apache.org">user@esme.apache.org</a> and <a href="mailto:dev@esme.apache.org">dev@esme.apache.org</a> along
+with updating the "Last Updated" date at the top of this page.</p>
+<p>If there are any questions regarding this privacy policy, you can contact
+us on the following mailing list <a href="mailto:private@esme.apache.org">private@esme.apache.org</a>.</p>
+<p>Sincerely,
+The Apache ESME PMC</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/existing-public-esme-installations.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/existing-public-esme-installations.cwiki (added)
+++ websites/staging/esme/trunk/content/existing-public-esme-installations.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,5 @@
+There are different public ESME installations: they are showcases, how an ESME setup looks like.
+
+There is not the only public production-quality ESME setup, as ESME is intended to serve as an inhouse (read: behind-firewall) microblogging system.(see ESME's [differentation from other microblogging platforms|Differentiation])
+* [http://www.esme.us/esme/]: this site hosts also the ESME blog (at [http://blog.esme.us/]). This installation is used by many people from the development team. The layout of this site does not reflect the current SVN version. This site is based on our initial UI
+* [http://esmecloudserver.dickhirsch.staxapps.net/index] and [http://esmecloudserverapache.dickhirsch.staxapps.net/] use the cloud based infrastucture from [http://stax.net] and reflect the current version in the project's SVN. The stax setups are updated regularly from SVN and are used to showcase new functions. Additionally [loadtesting|Loadtesting] takes place on these installations. The Stax server acts as a public server that displays the most recent apache svn source code and thus it isn't bug free. It is usually updated once a week.
\ No newline at end of file
Added: websites/staging/esme/trunk/content/existing-public-esme-installations.html
==============================================================================
--- websites/staging/esme/trunk/content/existing-public-esme-installations.html (added)
+++ websites/staging/esme/trunk/content/existing-public-esme-installations.html Mon Jun 27 13:55:28 2011
@@ -0,0 +1,93 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/css/esme.css" rel="stylesheet" type="text/css">
+ <title>Apache ESME - Existing public ESME installations</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <link rel="icon" type="image/png" href="/images/esme-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+ <div id="navigation">
+ <img alt="Apache ESME" width="220" height="101" src="/images/esme-logo/esme-powerd.gif"/>
+ <h1 id="esme_links">ESME links</h1>
+<ul>
+<li><a href="/index.html">Home</a></li>
+<li><a href="/team.html">Project Team</a></li>
+<li><a href="/docs/buildfromSVN.html">Building ESME</a></li>
+<li><a href="/docs/faq.html">FAQ</a></li>
+<li><a href="/docs/actions.html">Actions</a></li>
+<li><a href="/docs/apis.html">APIs</a></li>
+<li><a href="/docs/clients.html">Clients</a></li>
+<li><a href="/docs/collaboration.html">Collaboration</a></li>
+<li><a href="/docs/install.html">Installation Guides</a></li>
+<li><a href="/docs/yql.html">YQL</a><br />
+</li>
+</ul>
+<h1 id="asf_links">ASF links</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Existing public ESME installations</h1>
+ <p>There are different public ESME installations: they are showcases, how an
+ESME setup looks like.</p>
+<dl>
+<dt>There is not the only public production-quality ESME setup, as ESME is</dt>
+<dt>intended to serve as an inhouse (read: behind-firewall) microblogging</dt>
+<dt>system.(see ESME's <a href="differentiation.html">differentation from other microblogging platforms</a></dt>
+<dt>)</dt>
+<dt>* <a href="http://www.esme.us/esme/">http://www.esme.us/esme/</a></dt>
+<dd>this site hosts also the ESME blog (at [http://blog.esme.us/]</dd>
+</dl>
+<p>). This installation is used by many people from the development team. The
+layout of this site does not reflect the current SVN version. This site is
+based on our initial UI
+* <a href="http://esmecloudserver.dickhirsch.staxapps.net/index">http://esmecloudserver.dickhirsch.staxapps.net/index</a>
+ and [http://esmecloudserverapache.dickhirsch.staxapps.net/]
+ use the cloud based infrastucture from [http://stax.net]
+ and reflect the current version in the project's SVN. The stax setups are
+updated regularly from SVN and are used to showcase new functions.
+Additionally [loadtesting|Loadtesting]
+ takes place on these installations. The Stax server acts as a public
+server that displays the most recent apache svn source code and thus it
+isn't bug free. It is usually updated once a week.</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, ESME and the Apache feather and ESME logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/esme/trunk/content/faq.cwiki
==============================================================================
--- websites/staging/esme/trunk/content/faq.cwiki (added)
+++ websites/staging/esme/trunk/content/faq.cwiki Mon Jun 27 13:55:28 2011
@@ -0,0 +1,219 @@
+{section}{column:width=70%}
+
+h1. Questions
+
+h2. General
+
+[Can I use OpenJDK and ESME together?|#OPENJDK1]
+
+[Why can't you delete messages in ESME?|#delete1]
+
+[On which J2EE containers has ESME been tested?|#J2EE_container1]
+
+[How does search work in ESME?|#compass1]
+
+[How do you configure OpenID?|#openid1]
+
+[Does ESME support LDAP integration?|#ldap1]
+
+[Does ESME work with JDK 1.5|#JDK_1.5_1]
+
+[How do you start jetty with a different port when using maven?|#maven_1]
+
+[How do you run ESME in production-mode?|#prod_1]
+
+[How do you run ESME with CURL?|#curl_1]
+
+
+
+h2. Design-related
+
+[How does Twitter's new streaming API differ from ESME's design?|#twitter_api1]
+
+[In an enterprise context could it be an requirement to send a link to someone else pointing to a specific potentially old message in a certain Pool. How would this work?|#design1]
+
+[Would it be costly in your model to get the message nr. X ( n older messages) in a users' timeline?|#design2]
+
+[I don't get why it has to be in the session's state because you could as well use the information that a user is online as a guidance, even if the state would be stored somewhere out of the session. Wouldn't make a difference I guess and storing it in the session looks natural.|#design3]
+
+[I don't understand why ESME would need to store all entries in a cache, instead of only keeping the last n entries for each user based on some heuristics such as the last 3 days or something. I would somehow expect that the probability that a user wants to see a message is exponentially decreasing with the messages age. For example that someone wants to see a message that is the 1000 newest message in his timeline is probably almost zero|#design4].
+
+
+h2. Actions
+
+[How do I add a content type to a HTTP Post action?|#action_content_type1]
+
+
+
+
+
+
+
+h2. Platform Specific
+
+
+h3. Apple
+
+[Are there are tips for building on Apples?|#apple1]
+
+
+----
+----
+h1. Answers
+
+
+h2. General
+
+*Can I use OpenJDK and ESME together?* {anchor:OPENJDK1}
+
+Don't use OpenJDK and ESME together. YUI compressor fails with OpenJDK.
+
+----
+*Why can't you delete messages in ESME?* {anchor:delete1}
+
+There is a long discussion of the dangers of [deleting messages |ESME:Message Deletion] on the mailing list.
+
+
+----
+*On which J2EE containers has ESME been tested?* {anchor:J2EE_container1}
+
+* Tomcat
+* Jetty
+* SAP Netweaver CE
+* Glassfish
+
+----
+*How does search work in ESME?* {anchor:compass1}
+
+ESME uses [Compass|http://www.compass-project.org/]to perform full-text searches.
+
+*Selecting different usage patterns*
+
+There are different ways to use compass in ESME. The selection of which approach to use depends on what your requirements are.
+
+To select the option that you wish to use, you must set this option in [your property file|ESME:Server Configuration]. To set the option, please use the following syntax:
+{code}
+compass_config_file=/props/compass.filesystem.cfg.xml
+{code}
+Currently, there are three examples of different compass based options in the _/server/src/main/resources/props/ folder._
+|| File name || Description ||
+| compass.filesystem.cfg.xml | Using the file system to store index related data |
+| compass.jdbc.cfg.xml | Using the a database to store index related data - access via JDBC |
+| compass.jndi.cfg.xml | Using the a database to store index related data - access via JNDI |
+
+----
+*How do you configure OpenID?* {anchor:openid1}
+
+_Using a proxy with OpenID_
+
+Often you may wish to install ESME behind the firewall. In most cases, you won't have an internal OpenId provider, which means that your users are going to use OpenIds from external providers. Usually, you will have to go through an internal proxy.
+
+If this is the case, then you must set the proxy server. To do this use [the property file|ESME:Server Configuration], This file must include the following lines:
+{code}
+http.proxyHost=[proxy - look in your browser]
+http.proxyPort=[proxy port - look in your browser]
+{code}
+----
+*Does ESME support LDAP integration?* {anchor:ldap1}
+
+Currently, ESME doesn't support LDAP usage. We are looking at a new [LDAP component for lift|http://jgoday.wordpress.com/2009/11/27/lift-ldap/]as the basis for our implementation.
+----
+*Does ESME work with JDK 1.5{*}*?* {anchor:JDK_1.5_1}
+
+Currently, there are some issues dealing with JDK 1.5. Many of these issues are related to restrictions associated with Scala itself.
+----
+*How do you start jetty with a different port when using maven?* {anchor:maven_1}
+
+_mvn jetty:run \-Djetty.port=8081_
+----
+*How do you run ESME in production-mode?* {anchor:prod_1}
+
+Start the container with the following environment variable (from lift list) _\-Drun.mode=production_
+----
+*How do you run ESME with CURL?* {anchor:curl_1}
+
+_Step-0: Generate Token:_Login to ESME via WebGui and used the Tokens menu at the top to create a new token_.
+
+_Step-1:Construct the curl command:_Here is my example\-_curl \-X POST \-v \-u \[your user id\]:\[your token from step-0\] \-d status="my curl message on feb 24"[http://localhost:8080/esme/twitter/statuses/update.xml|http://localhost:8080/esme/twitter/statuses/update.xml]
+
+My ESME has 'esme' context running in Jetty. I didn't make any config change and is the default deployment. My WebGUI login is,[http://localhost:8080/esme/|http://localhost:8080/esme/]
+
+
+_Step-2: Execute curl command_:
+Make sure you have curl installed on your system. My system is Ubuntu. Cut n paste the curl command in the terminal and hit enter. (For convenience you can keep your WebGui running to check the message).
+After you hit enter, you should get 200 ok status from the server and a XML response. You can check the new message in the WebGUI and it updates REAL TIME\! ( no refresh needed)
+
+
+Run multiple times curl to see the updates in WebGui. I used Firefox.
+
+
+
+h2. Design-related
+
+*How does Twitter's new streaming API differ from ESME's design?* {anchor:twitter_api1}
+
+Twitter now has another take on a message-streaming API over HTTP, using what looks like a non-HTTP-1.1-compliant form of request pipelining (sending multiple responses over a single open connection). See the documentation at [http://apiwiki.twitter.com/Streaming-API-Documentation|http://apiwiki.twitter.com/Streaming-API-Documentation]
+
+The advantage of their mechanism is that it's a smoother experience. What we've done with chunking/long polling is to simulate a stream of data on top of a non-streaming protocol. What Twitter has done is to say "this is a one-way conversation, we've got an open TCP/IP connection, so let's use it." Implementing what they have would require going below the current set of abstractions that Lift provides above the Servlets.
+At a practical level, the difference is at one layer... the one dealing with the HTTP requests. At the layers above, events flow either way.
+
+At the basic philosophical level, Twitter's implementation is purer. It treats a stream of information as a stream of information.
+I like it, but I'm not sure what the benefits would be vs. the development costs of implementing such a mechanism (unless there's an en mass migration of microblogging clients to such a mechanism).
+
+A significant disadvantage of Twitter's design is the requirement of only one streaming connection per account. As much as I dislike the approach of using session cookies to uniquely identify API message
+queues, it is a heck of a lot better than what is going to happen when Twitter clients start to implement this API, which will be:
+1. I log in with Seesmic Web (which has implemented the Twitter streaming API)
+2. I receive messages 1, 2, and 3.
+3. I log in on a different computer with Twhirl (which has also
+implemented the Twitter streaming API)
+(3.1 Twitter disconnects the Seesmic connection invisibly from the user)
+4. I receive message 4 in Twhirl
+(4.1 Seesmic tries to reconnect, which results in Twhirl being disconnected)
+5. I receive message 5 in Seesmic
+6. And so on....
+End result: 1 really confused user trying to connect from two banned IP addresses.
+I think this is a good illustration of why we need some client-specific identifier for a streaming/delta-queue API. It doesn't need to be a session, but that's working pretty nicely for now.
+I would prefer to stick with what Lift provides for the moment. I need to do the conceptual exercise, but on first glance I don't think Twitter's approach results in much of a gain over our approach. Fewer
+connection attempts, which will help a lot at Twitter-scale, but which I'm not sure makes a big difference at Enterprise-scale.
+Another drawback (and I'm really not sure on this one) is that I don't think a lot of HTTP client libraries give easy access to a request that is still open. The design of the queue API is extremely simple from a client programming perspective. I think that's a big upside.
+
+h2.
+
+----
+*Question: In an enterprise context it could be an requirement to send a link to someone else pointing to a specific potentially old message in a certain Pool.* {anchor:design1}
+
+Yes. That's perfectly reasonable. That message is like a static file on disk. Once it's written, it remains unchanged until it's deleted. This is an ideal application of a REST-style approach. That's why I've advocated
+for a "message based" approach first, but a REST/static approach when the message based approach doesn't make sense. What I am opposed to is a "try to make everything fit the REST model" approach to API design.
+----
+*Question: Would it be costly in your model to get the message nr. X (\+ n older messages) in a users timeline?* {anchor:design2}
+A message will exist outside of a timeline. There exists a cache of recently accessed messages. Sometimes there will be a historic message that is referenced and that will be materialized from backing store and rendered. It will likely fall out of cache if it's historical and not accessed again.
+----
+*Question: I don't get why it has to be in the session's state because you could as well use the information that a user is online as a guidance, even if the state would be stored somewhere out of the session. Wouldn't make a difference I guess and storing it in the session looks natural.* {anchor:design3}
+
+The state itself is not in the session. The session is the guide that the user is online. The session contains a listener that is attached to the User. The only real state that resides in the session is the state
+necessary to batch up any messages that the User has forwarded to the listener in between the HTTP polling requests. If there is an HTML front end, state about that front end will reside in the session as well, but
+that's a different issue.
+----
+*Question: I don't understand why we would need to store all entries in a cache, instead of only keeping the last n entries for each user based on some heuristics such as the last 3 days or something. I would somehow expect that the probability that a user wants to see a message is exponentially decreasing with the messages age. For example that someone wants to see a message that is the 1000 newest message in his timeline is probably almost zero.* {anchor:design4}
+Some people mine their timelines for information. I agree that some aging policy is necessary as 36B entries will consume a lot of storage in RAM or on disk, but the last 1,000 is likely too few based on what I have seen of actual user behavior.
+In terms of an aging policy in an RDBMS, the cost of aging out old entries is likely to be an index scan or something on that order (DELETE FROM mailbox WHERE date < xxx or a user-by-user DELETE WHERE id IN (SELECT messages > 1000 in mailbox))
+
+h2. Actions
+
+*How do I add a content type to a HTTP Post action?* {anchor:action_content_type1}
+{code}
+http://localhost:1234
+header:Content-Type=text%2fxml
+<text>%s</text>
+{code}
+
+h2. Platform Specific
+
+h3. Apple
+
+*Are there are tips for building on Apples?* {anchor:apple1}
+
+Usually, JDK 6 is the best choice. JDK 5 currently doesn't work
+----
+{column}{column:width=30%}{*}Table of Contents*
+{toc:mminLevel=3}{column}{section}
\ No newline at end of file