Hello - Any project updates?

56 views
Skip to first unread message

Andres Rodriguez

unread,
May 10, 2013, 6:35:25 PM5/10/13
to te...@googlegroups.com
Hello, hope all is well with this project.  I have been following it on and off, and I think it is the most wonderful alternative
to all the people that do not want to die in the callback nightmare that is node.js. Is this project being advanced?  Is there
anything I could do to help?

Thanks!


Andres

Ondřej Žára

unread,
May 13, 2013, 6:37:08 AM5/13/13
to te...@googlegroups.com
Hi Andres,

thanks for your e-mail. The project itself is doing fine: there are no pressing bugs or urgent feature requests. In fact, I personally do not see any imminent features and changes that need to be implemented; I am happy using TeaJS for my purposes and I am not missing any modules. If you request some new functionality (or bugfixes), please submit these via the Google Code issue tracker (or e-mail them using gmail or google groups).

It might look like TeaJS development is on halt now. While this is technically true, it is not related to lack of time/will/people etc; it just means that we (me) are happy with the status quo. I will try to get a speaker slot at jsconf.eu 2013 to promote TeaJS (and other alternative SSJS approaches) a bit; perhaps that might stir the (currently) calm waters.


Sincerely,
Ondrej Zara



2013/5/11 Andres Rodriguez <acro...@gmail.com>


Andres

--
You received this message because you are subscribed to the Google Groups "TeaJS (formerly v8cgi)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to teajs+un...@googlegroups.com.
To post to this group, send email to te...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/teajs/fe875402-c9c1-40a2-b880-04fd98901f4c%40googlegroups.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
+------------------+
|tn=b.             |
|p==n              |
|+j1               |
|=+                |
|1          #  ##  |
|           # #    |
|           #  ##  |
|        #  #    # |
|         ##   ##  |
+------------------+
 jsstyle.github.com
Message has been deleted

Ondřej Žára

unread,
Jul 1, 2013, 2:52:02 AM7/1/13
to te...@googlegroups.com
Hi Andres,

releasing a build of TeaJS with context reusing makes some sense, although the primary distribution method is a source code package.

Also please note that TeaJS does not focus mainly on performance (node's approach is - and will always be - faster by definition), so if you are looking for something to handle requests at light speed, perhaps TeaJS's architecture (i.e. interfacing to Apache) in not the way to go.

Finally, context reusing introduces some form of a security inconsistence, when a bad-behaving script can modify the built-in JS primordials for other scripts. In other words, context reusing shall be used only by one user (as opposed to a PHP shared hosting, for example).


Sincerely,
Ondrej Zara


2013/6/28 <alvaro...@gmail.com>
Hi,

I really see a lot of value and potential in TeaJS, the best SSJS I've seen.

One of its weaknesses is performance: using "ab", the Apache performance benchmark shows that the request served rate is not very high. I guess the startup time for each request is relatively high due to the JS engine starting every time. Node on the other hand has the JS engine up un running continuously. I saw your comment about reusing the V8 instance between requests, using a compile flag. Looks good. Maybe you can release a build with that feature enabled. Or is it not stable enough?

Also updating the version of V8 might help.

I'll post more ideas as feature requests as you suggest.


Thank you!

For more options, visit https://groups.google.com/groups/opt_out.
 
 

niknah

unread,
Jul 5, 2013, 1:20:30 AM7/5/13
to te...@googlegroups.com
If you do a test with not much in the script, node will be very fast, since it doesn't do anything apache stuff like logging, checking for access permissions, etc.  But when you put lots of stuff in the script, the speed of handling the request doesn't matter as much as the speed of processing the template, database, etc.

But I don't feel apache is to blame, if you compare a plain php request on apache vs teajs on apache.  teajs is slower.

I've used node & teajs, they both occassionally crash.
The difference is that node completely crashes for everyone.  teajs only crashes for one request and it's ok again when the user presses reload.

Ondřej Žára

unread,
Jul 5, 2013, 2:43:17 PM7/5/13
to te...@googlegroups.com
Well, I use TeaJS mainly as a scripting language to do daily tasks using shellscripts. In my opinion, the speed penalty (when compared to PHP) might be caused by the need to create a fresh JS context for every request - something which probably does not happen in PHP world. Context reusing is designed to remedy this.

It might be also feasible to implement a webserver in TeaJS itself, similarly to what node does - to see if the context creation / apache communication is indeed a bottleneck.


Sincerely,
Ondrej Zara


2013/7/5 niknah <nik...@gmail.com>

For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply all
Reply to author
Forward
0 new messages