Re: T5 : potential feature - JSON component

2007-06-28 Thread #Cyrille37#

Hello,

I'm interesting by the subject. How to integrate JSON with Tap5 in a 
nice way.


For the moment I'm using http://oss.metaparadigm.com/jsonrpc/ to 
communicate between Java Applets and WebApps.
But I didn't integrate it in Tapestry ; I'm using the JSonRpc Servlet 
and share objects with WebApps using SpringFramework.


It would be nice to get Tapestry managing JSonRpc calls.

I'm new with Tapestry, and Java in general, so I could not bring any 
idea about the way to do this.

But I can participate to the discussion and make some tryies.

cyrille

Evan Rawson - Work a écrit :
It would be great if a JSON component could be created for T5. After some extensive research i feel that this feature really would add a ton of flexibility of how your tapestry application can communicate with other tapestry application running on a network. For example my company needs to split up our monstrous application now consisting of about 700 to 1000 pages, and and a few thousand components. We are branching off our sub applications to run as there own independent application. The ability to allow these separate application to talk to each other is very ambigious, meaning that we need to transfer data via http sessions or via a db. 


with the implementation of JSON we could easily setup a java component service 
which could allow another tapestry application to request data from another 
server by giving it the domain, app name, and service name (what you wanna look 
up)

due to JSON 's extreme flexibility and speed, tapestry applicatiosn powered by 
JSON could allow our application to talk to and interact with pretty much any 
other application coded in any modern language. wether it be another web 
application or backend process, or even a desktop application.

i believe that JSON would be a better langauge versus say XML becuase its 
parser is faster, and its easier to intrepret in human language. JSON is also a 
more superior way to handle AJAX requests rather then using XML streams. 
(smaller size, and faster to parse)

just a thought.

~evan
  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: T5 : potential feature - JSON component

2007-06-28 Thread Evan Rawson - Work
it really wouldn't be that hard. basically you would create a java class to 
generate your RPC calls and internally within your java app it would share 
data via java objects. i believe they would be serialized so you could 
easily access and share them.


the bulk of the work would be having the tapestry java component generate 
the resource location on the fly when an external service is invoked. Kinda 
like how AJAX invokes an XML document on the fly.


i completely forgot about applets. We dont usually use them at work so i 
always forget. go figure. Anyways, the ability to easily allow applets to 
communicate with a java backend running on a servcer would be amazing 
powerful. forexample, you could use your applet to handle only UI data and 
other smaller processes which the client side could handle. have it 
communicate directly with a java app running on the backend which could be 
hooked up to a mainframe or network which could be used to massive rendering 
jobs or datamining.


a possible use of this integration would be a realtime, high resolution 
rendering of say a molecule, CAD drawing, or 3d animation accesable from the 
web. The server could process the rendering and outputs the frames to a dir, 
you could have the applet pick up the frames via JSON (IE. passing the 
applet the URI of the rendered frames, then have the applet sequence them. A 
fbig enough mainframe could even cahce the rendered frames and map them to a 
URI.  This could open up tapestry with the ability to program and host say a 
Web based 3d rendering program such as Maya or something. The possibilities 
are endless.


~evan




- Original Message - 
From: #Cyrille37# [EMAIL PROTECTED]

To: Tapestry users users@tapestry.apache.org
Sent: Thursday, June 28, 2007 1:28 PM
Subject: Re: T5 : potential feature - JSON component


Hello,

I'm interesting by the subject. How to integrate JSON with Tap5 in a
nice way.

For the moment I'm using http://oss.metaparadigm.com/jsonrpc/ to
communicate between Java Applets and WebApps.
But I didn't integrate it in Tapestry ; I'm using the JSonRpc Servlet
and share objects with WebApps using SpringFramework.

It would be nice to get Tapestry managing JSonRpc calls.

I'm new with Tapestry, and Java in general, so I could not bring any
idea about the way to do this.
But I can participate to the discussion and make some tryies.

cyrille

Evan Rawson - Work a écrit :
It would be great if a JSON component could be created for T5. After some 
extensive research i feel that this feature really would add a ton of 
flexibility of how your tapestry application can communicate with other 
tapestry application running on a network. For example my company needs to 
split up our monstrous application now consisting of about 700 to 1000 
pages, and and a few thousand components. We are branching off our sub 
applications to run as there own independent application. The ability to 
allow these separate application to talk to each other is very ambigious, 
meaning that we need to transfer data via http sessions or via a db.
with the implementation of JSON we could easily setup a java component 
service which could allow another tapestry application to request data 
from another server by giving it the domain, app name, and service name 
(what you wanna look up)


due to JSON 's extreme flexibility and speed, tapestry applicatiosn 
powered by JSON could allow our application to talk to and interact with 
pretty much any other application coded in any modern language. wether it 
be another web application or backend process, or even a desktop 
application.


i believe that JSON would be a better langauge versus say XML becuase its 
parser is faster, and its easier to intrepret in human language. JSON is 
also a more superior way to handle AJAX requests rather then using XML 
streams. (smaller size, and faster to parse)


just a thought.

~evan





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: T5 : potential feature - JSON component

2007-06-28 Thread #Cyrille37#


I spoke about Java Applet, but we can think about Macromedia Flash too. 
Flash is a really nice technology.


If JSon is implemented in Tapestry like every great Tapestry designs, it 
should be very easy to add more protocols !!


cyrille.

Evan Rawson - Work a écrit :
it really wouldn't be that hard. basically you would create a java 
class to generate your RPC calls and internally within your java app 
it would share data via java objects. i believe they would be 
serialized so you could easily access and share them.


the bulk of the work would be having the tapestry java component 
generate the resource location on the fly when an external service is 
invoked. Kinda like how AJAX invokes an XML document on the fly.


i completely forgot about applets. We dont usually use them at work so 
i always forget. go figure. Anyways, the ability to easily allow 
applets to communicate with a java backend running on a servcer would 
be amazing powerful. forexample, you could use your applet to handle 
only UI data and other smaller processes which the client side could 
handle. have it communicate directly with a java app running on the 
backend which could be hooked up to a mainframe or network which could 
be used to massive rendering jobs or datamining.


a possible use of this integration would be a realtime, high 
resolution rendering of say a molecule, CAD drawing, or 3d animation 
accesable from the web. The server could process the rendering and 
outputs the frames to a dir, you could have the applet pick up the 
frames via JSON (IE. passing the applet the URI of the rendered 
frames, then have the applet sequence them. A fbig enough mainframe 
could even cahce the rendered frames and map them to a URI.  This 
could open up tapestry with the ability to program and host say a Web 
based 3d rendering program such as Maya or something. The 
possibilities are endless.


~evan




- Original Message - From: #Cyrille37# [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Thursday, June 28, 2007 1:28 PM
Subject: Re: T5 : potential feature - JSON component


Hello,

I'm interesting by the subject. How to integrate JSON with Tap5 in a
nice way.

For the moment I'm using http://oss.metaparadigm.com/jsonrpc/ to
communicate between Java Applets and WebApps.
But I didn't integrate it in Tapestry ; I'm using the JSonRpc Servlet
and share objects with WebApps using SpringFramework.

It would be nice to get Tapestry managing JSonRpc calls.

I'm new with Tapestry, and Java in general, so I could not bring any
idea about the way to do this.
But I can participate to the discussion and make some tryies.

cyrille

Evan Rawson - Work a écrit :
It would be great if a JSON component could be created for T5. After 
some extensive research i feel that this feature really would add a 
ton of flexibility of how your tapestry application can communicate 
with other tapestry application running on a network. For example my 
company needs to split up our monstrous application now consisting of 
about 700 to 1000 pages, and and a few thousand components. We are 
branching off our sub applications to run as there own independent 
application. The ability to allow these separate application to talk 
to each other is very ambigious, meaning that we need to transfer 
data via http sessions or via a db.
with the implementation of JSON we could easily setup a java 
component service which could allow another tapestry application to 
request data from another server by giving it the domain, app name, 
and service name (what you wanna look up)


due to JSON 's extreme flexibility and speed, tapestry applicatiosn 
powered by JSON could allow our application to talk to and interact 
with pretty much any other application coded in any modern language. 
wether it be another web application or backend process, or even a 
desktop application.


i believe that JSON would be a better langauge versus say XML becuase 
its parser is faster, and its easier to intrepret in human language. 
JSON is also a more superior way to handle AJAX requests rather then 
using XML streams. (smaller size, and faster to parse)


just a thought.

~evan








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: T5 : potential feature - JSON component

2007-06-28 Thread Evan Rawson - Work
thanx for bringing that up. flash would be really nice as well, that could 
expand alot of the UI. however i really think AJAX is gonna take over flash 
as more and more things are discovered which you can do with AJAX. flash is 
kewl, but its also plugin dependent where as AJAX works on any JS compliant 
browser. ive been in the process of writing my own flash data stream to 
handle content via parameters, but a JSON implementation would be much more 
superior as you can grab whatever data from any tapestry external JSON 
service you have created on your application.


i suppose in a way JSON would also allow for any other future technologies 
to be easily plugable into an existing tapestry application without the need 
for serious UI overhaul.


this talk abotu flash gives me the proposal of creating a flash only UI, and 
have a tapestry application running on the backend handling all DB queries, 
scheeduled jobs, or any other processor intense process. you could even have 
tapestry manage all of your flash resources and call the resources directly 
withi flash via JSON. I could really see this open up a new scope for the 
scalbility of flash applications. typically now you are limited to the base 
size of your flash application. meaning if you have to many resources in 
your flash movie it will take forever to download and run. whereas you could 
have tapestry manage your backend and resources and have flash call whatever 
resources it needs on the fly. this could be quite powerful.


i mean you can do this already, but the frameworks are which can handle this 
aren't as robust and easy to use as tapestry is. tapestry is also pretty 
fast and efficent at managing resources, along with your httpsession. this 
could really extend flash technologies to a new level.


evan
- Original Message - 
From: #Cyrille37# [EMAIL PROTECTED]

To: Tapestry users users@tapestry.apache.org
Sent: Thursday, June 28, 2007 2:37 PM
Subject: Re: T5 : potential feature - JSON component



I spoke about Java Applet, but we can think about Macromedia Flash too.
Flash is a really nice technology.

If JSon is implemented in Tapestry like every great Tapestry designs, it
should be very easy to add more protocols !!

cyrille.

Evan Rawson - Work a écrit :
it really wouldn't be that hard. basically you would create a java class 
to generate your RPC calls and internally within your java app it would 
share data via java objects. i believe they would be serialized so you 
could easily access and share them.


the bulk of the work would be having the tapestry java component generate 
the resource location on the fly when an external service is invoked. 
Kinda like how AJAX invokes an XML document on the fly.


i completely forgot about applets. We dont usually use them at work so i 
always forget. go figure. Anyways, the ability to easily allow applets to 
communicate with a java backend running on a servcer would be amazing 
powerful. forexample, you could use your applet to handle only UI data and 
other smaller processes which the client side could handle. have it 
communicate directly with a java app running on the backend which could be 
hooked up to a mainframe or network which could be used to massive 
rendering jobs or datamining.


a possible use of this integration would be a realtime, high resolution 
rendering of say a molecule, CAD drawing, or 3d animation accesable from 
the web. The server could process the rendering and outputs the frames to 
a dir, you could have the applet pick up the frames via JSON (IE. passing 
the applet the URI of the rendered frames, then have the applet sequence 
them. A fbig enough mainframe could even cahce the rendered frames and map 
them to a URI.  This could open up tapestry with the ability to program 
and host say a Web based 3d rendering program such as Maya or something. 
The possibilities are endless.


~evan




- Original Message - From: #Cyrille37# [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Thursday, June 28, 2007 1:28 PM
Subject: Re: T5 : potential feature - JSON component


Hello,

I'm interesting by the subject. How to integrate JSON with Tap5 in a
nice way.

For the moment I'm using http://oss.metaparadigm.com/jsonrpc/ to
communicate between Java Applets and WebApps.
But I didn't integrate it in Tapestry ; I'm using the JSonRpc Servlet
and share objects with WebApps using SpringFramework.

It would be nice to get Tapestry managing JSonRpc calls.

I'm new with Tapestry, and Java in general, so I could not bring any
idea about the way to do this.
But I can participate to the discussion and make some tryies.

cyrille

Evan Rawson - Work a écrit :
It would be great if a JSON component could be created for T5. After some 
extensive research i feel that this feature really would add a ton of 
flexibility of how your tapestry application can communicate with other 
tapestry application running on a network. For example my company needs